Enhanced Dispenser Control

ABSTRACT

A scent dispenser may comprise a vial retaining mechanism, a heating element, vial sensor, and a controller. The vial retaining mechanism includes a vial coupling that removeably retains a vial containing a scented solution. The includes a wick extending from a cavity of the vial through an opening of a neck of the vial. The heating element is shaped to receive and heat the wick of the vial. The vial sensor includes an array of sensor pads that are arranged in alignment with the vial retained by the vial coupling. The controller is electrically coupled to the heating element and electrically coupled to the array of sensor pads. The controller regulates a temperature level of the heating element, and receives signals from the array of sensor pads and processing the signals to determine a fluid level of the vial.

BACKGROUND

The present disclosure relates to scent dispensation.

Existing solutions for dispensing scents within a location, such as ahome, include conventional scented candles, incense stocks, hanging airfresheners, and electric fragrance diffusers, such as those that pluginto an outlet socket and include a heating element to heat a fragrantsubstance. In some cases, a porous substrate is saturated with thefragrant substance and then placed adjacent to a heat source, whichheats up the fragrant substance to diffuse it within a predeterminedspace.

While functional, these solutions are limited. For example, it is oftendifficult to tell when a fragrance dispenser has run out of fragrance,as the dispenser typically lacks any sort of indicator and one is leftto smell the dispenser manually to determine how much fragrance isactually left, which is ineffective as the dispenser itself may stillsmell like the diffuse fragrance up close that may have little effect inthe area that is to be perfumed. In addition, if the users wishes tochange a fragrance, the user has to manually open the dispenser toreplace the cartridge in the dispenser, or in the case of hangingdispensers, replace it with a fresh version.

Existing scent dispensers also provide little control to users toconfigure how much scent is actually being diffused. Some existingelectronic scent dispensers include a hardware selector to switch thedevice between off, low, and high operating states. However, theseelectronic scent dispensers are not self-aware, and therefore output thesame amount of scent over time. Therefore, even at a low setting, thescent dispenser can eventually over-perfume a room, and only changestate when manually switched off or set to another level by the userusing the switch. This results in the unpleasant experience of the roombecoming too perfumed and, in some cases, causes people to leave theroom.

SUMMARY

According to one innovative aspect of the subject matter being describedin this disclosure, an example system includes a first vial including afirst side, one or more sidewalls, and a second side. The one or moresidewalls connect the first side to the second side. The first side, theone or more sidewalls, and the second side collectively form an innercavity. The first side includes an opening through which a solutioncontainable in the inner cavity is dispensed from the first vial. Thesystem includes a vial sensor including a first array of sensor padselectrically coupled to a controller, a sidewall from the one or moresidewalls of the first vial being situated adjacent to the first arrayof sensor pads within a first array of electric fields. The first arrayof sensor pads are electrically charged to produce the first array ofelectric fields. The controller detects changes in one or more of theelectric fields of the first array as the solution is dispensed from thefirst vial.

In general, the system may optionally include one or more of thefollowing features: a second vial including a first side, one or moresidewalls, a second side; that the one or more sidewalls of the secondvial connect the first side of the second vial to the second side of thesecond vial; that the first side of the second vial, the one or moresidewalls of the second vial, and the second side of the second vialcollectively form an inner cavity of the second vial; that the firstside of the second vial includes an opening through which a secondsolution containable in the inner cavity is dispensed from the secondvial; that the first array of sensor pads are situated along a firstside of the vial sensor; that the vial sensor includes a second array ofsensor pads electrically coupled to the controller and situated along asecond side of the vial sensor situated located adjacent to the firstside of the vial sensor; that a sidewall from the one or more sidewallsof the second vial is situated adjacent to the second array of sensorpads with a second array of electric fields; that the second array ofsensor pads is electrically charged to produce the second array ofelectric fields; that the controller detects changes in the one or moreof the electric fields of the second array as the second solution isdispensed from the second vial; a vial retaining mechanism including afirst vial coupling and a second vial coupling; that the first vialcoupling receives and detachably retains the first side of the firstvial, and the second vial coupling receives and detachably retains thefirst side of the second vial; that the first side of the first vialincludes a neck through which the opening of the first side of the firstvial extends; that the first side of the second vial includes a neckthrough which the opening of the first side of the second vial extends;that the first vial coupling includes one or more surfaces shaped toengage with and secure the neck of the first side of the first vial;that the second vial coupling includes one or more surfaces shaped toengage with and secure the neck of the first side of the second vial;that the vial retaining mechanism includes a first wick receiver and asecond wick receiver; that the first wick receiver includes a stoppingmember having a wick hole extending through the stopping member of thefirst wick receiver; that the second wick receiver includes a stoppingmember having a wick hole extending through the stopping member of thesecond wick receiver; that the wick hole of the first wick receiverreceives a wick extending outwardly from the opening of the first sideof the first vial; that the wick hole of the second wick receiverreceives a wick extending outwardly from the opening of the first sideof the second vial; a first heating element situated on a side of thestopping member opposing the first vial; a second heating elementsituated on the side of the stopping member opposing the second vial;that the first heating element heats an end of the wick extendingthrough the wick hole of the first wick receiver, and the second heatingelement heats an end of the wick extending through the wick hole of thesecond wick receiver; that the first heating element includes a ringthat receives the end of the wick extending through the wick hole of thefirst wick receiver; that the second heating element includes a ringthat receives the end of the wick extending through the wick hole of thesecond wick receiver; that the first heating element and the secondheating element are formed at least in part of a ceramic material; afirst vial coupling that receives and detachably retains the first vial;a heating element that heats the solution receivable from the firstvial; a housing that houses the first vial coupling, the heatingelement, and the vial sensor; that a front side of the housing includesan opening providing access to the first vial; a removable cover that,when attached to the front side of the housing, covers the openingproviding access to the first vial; that the removable cover includesone or more first magnetic fasteners; and that the front side of thehousing includes one or more second magnetic fasteners that arecompatible with the one or more first magnetic fasteners and thatmagnetically engage with the one or more first magnetic fasteners whenthe removable cover is situated abuttingly with the front side of thehousing.

In general, according to a further innovative aspect, an example systemincludes a vial retaining system, a heating element, a vial sensor, anda controller. The vial retaining mechanism includes a vial coupling thatremoveably retains a vial containing a scented solution. The vialincludes a neck forming an opening, a hollow body forming a cavitycontaining the scented solution, and a wick extending from the cavitythrough the opening of the neck. The heating element is shaped toreceive and heat the wick of the vial. The vial sensor includes an arrayof sensor pads that are arranged in alignment with the vial retained bythe vial coupling. The controller is electrically coupled to the heatingelement and electrically coupled to the array of sensor pads. Thecontroller regulates a temperature level of the heating element. Thecontroller receives signals from the array of sensor pads and processingthe signals to determine a fluid level of the vial.

In general, the system may optionally include one or more of thefollowing features: that the wick passes the scented solution to theheating element; that the heating element diffuses the scented solutionby heating the scented solution to the temperature level regulated bythe controller; that the controller electrically charges the sensor padsof the array; and that the controller detects a change in the signalsreceived from the array of sensor pads charged by the controller anddetermines a corresponding change in the fluid level of the scentedsolution of the vial; the change in the signals is a change incapacitance of at least one of the sensor pads; that the signals from afirst subset of the sensor pads reflect a maximum capacitance level;that the signals from a second subset of the sensor pads of the arrayreflect a minimum capacitance level; and that the controller determinesthe fluid level of the vial based on the signals from the first subsetand the signals from the second subset; that the sensor pads comprisecopper pads; that the vial coupling includes one or more fastenersformed to detachably engage with the neck of the vial; that the one ormore fasteners include one or more clips;

In general, according to a further innovative aspect, an example systemincludes a vial retaining system, two or more heating elements, a vialsensor, and a controller. The vial retaining mechanism includes two ormore vial couplings that removeably retain two or more vials. The two ormore vials each include a neck forming an opening, a hollow body forminga cavity, and a wick extending from the cavity through the opening ofthe neck. Each of the two or more heating elements are shaped to receiveand heat the wick of a corresponding vial of the two or more vials. Thevial sensor includes two or more arrays of sensor pads that arerespectively arranged in alignment with the two or more vials retainedby the two or more vial couplings. The controller is electricallycoupled to the two or more heating elements and electrically coupled toeach of the two or more arrays of sensor pads. The controller regulatesa temperature level of each of the two or more heating elements, and thecontroller receives signals from the arrays of sensor pads and processesthe signals to determine a fill level of each of the two or more vials.

Further innovative aspects include corresponding systems, methods,apparatus, and computer program products. These systems, methods,apparatus, computer program products, and other aspects, areparticularly advantageous in a number of respects. For example, thetechnology enables users to remotely control scent dispensers, switchbetween scents remotely, and receive notifications when a scent solutionis running/has run out, automatically switches the scent solution(s) todiffuse based on user location, allows users to schedule scent diffusionfor different locations, etc. In addition, the technology can collectdata about scent solution usage and user habits when using scentdispensers, and then analyze that data to produce analytics to informproducers about characteristics of the users, the scents being consumed,etc. Numerous additional features are also possible and contemplated,many of which are discussed herein.

However, this list of features and advantages is not all-inclusive andmany additional features and advantages are within the scope of thepresent disclosure. Moreover, it should be noted that the language usedin the present disclosure has been principally selected for readabilityand instructional purposes, and not to limit the scope of the subjectmatter disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating an example system for scentdispensation.

FIG. 1B is a block diagram illustrating an example scent dispenser.

FIG. 2A is a front perspective view of an example scent dispenser.

FIG. 2B is a rear perspective view of the example scent dispenser.

FIG. 2C is a front view of the example scent dispenser with a coverremoved.

FIG. 2D is a front exploded view of the example scent dispenser.

FIGS. 2E-2G are various further views of various components of theexample scent dispenser.

FIG. 3A is a schematic diagram of an example vial sensor.

FIG. 3B is a block diagram of an example vial sensor.

FIGS. 4A-4D are block diagrams depicting a progression for sensing asolution level of a vial using the vial sensor.

FIG. 5A is a front perspective view of an example vial with a wickinserted.

FIG. 5B is a front perspective view of the example vial with the wickremoved.

FIG. 6 is a flowchart of an example method for sensing vial volume.

FIG. 7A is flowchart of an example method for activating a vial.

FIG. 7B is flowchart of a further example method for activating a vial.

FIG. 8 is a flowchart of an example method for automatically adjustingthe dispensation intensity of a scent dispenser based on the presence ofnearby scent dispensers.

FIG. 9 is a flowchart of an example method for adjusting thedispensation intensity of a scent dispenser based on room size.

FIG. 10 is a flowchart of an example method for controlling operation ofscent dispenser(s) based on geolocation data.

FIG. 11 is a flowchart of an example method for scheduling scentdispensation for room(s) of a premises.

FIG. 12A is a flowchart of an example method for activating a scentdispenser based on detected motion.

FIG. 12B is a flowchart of an example method for using motion detectionto control operation of a scent dispenser.

FIG. 13 is a front perspective view of an example vial with a scannableoptical representation.

FIGS. 14A-14H are graphical representations of user interfaces forsetting up a scent dispenser.

FIGS. 15A-15H are graphical representations of user interfaces forconfiguring vial settings of a scent dispenser.

FIGS. 16A-16E are graphical representations of user interfaces forscheduling scent dispensation for one or more rooms.

FIG. 17 is a graphical representation of a user interface for viewingvial properties of an installed vial.

FIGS. 18A-18M are graphical representations of user interfaces ofelectronic marketplace for (re)ordering vials.

FIGS. 19A-19F are graphical representations of user interfaces forviewing and configuring room, schedule, and dispenser settings.

FIG. 20A is a graphical representation of a user interface forinstalling a new or replacement vial.

FIG. 20B is a graphical representation of a user interface for disablinggeolocation-based control of scent dispensation.

FIGS. 21-25 are schematic diagrams of various example components of ascent dispenser.

FIGS. 26-27B are graphical representations of example user interfacesfor display and receiving user interaction with scent analtyics.

DETAILED DESCRIPTION

The technology described in this disclosure relates to dispensing scentwithin the premises using remotely controllable scent dispensers. As anexample, the technology allows the user to remotely control theoperation of scent dispensers installed in his or her home using amobile application executed on a mobile device. Using the mobileapplication, the user may turn a scent dispenser on or off, change thescent that is being dispensed by the dispenser, change the intensitylevel of the scent dispensation, set a schedule for the scentdispensation, control the operation of the scent device based on thelocation of his/her mobile device, receive status notifications fromabout the operation of the scent dispenser, such as when a particularscent solution may be running out, etc.

FIG. 1A is a block diagram illustrating an example system 100 for scentdispensation. The system 100 may include one or more scent dispenserinstallations 158. In a typical implementation, a multiplicity of users112 may install scent dispenser on their respective premises 140 inwhich they wish to dispense various scents. A scent dispenserinstallation 158 may include any number of scent dispensers 132 a...132n. In the depicted implementation, scent dispensers 132 a and 132 n(individually or collectively also referred to as simply 132) areplugged into electrical sockets 146 a and 146 n. The scent dispensers132 may be located in the same room or in different rooms (e.g., 142 aand 142 n).

As shown, the illustrated system 100 further includes client device(s)106 and a server 150, which are electronically communicatively coupledvia a network 102 for interaction with one another, access point(s) 120,and the scent dispenser(s) 132, etc., using standard networkingprotocols, as reflected by signal lines 104, 138, and 152. In a typicalinstallation, the scent dispenser(s) 132 are coupled for electroniccommunication with the access point(s) 120 (e.g., a modem, router, etc.,coupled to the network 102) as reflected by signal lines 134 a and 134n. In further embodiments, the scent dispenser(s) 132 may be coupleddirectly to the network 102 as reflected by the signal line 138, such asvia a wireless wide area network (e.g., WWAN) or other suitable network.For clarity, reference to the term network 102 includes the localnetworks of the installations (e.g., provided by access point(s) 120,etc.), unless otherwise specified.

The scent dispenser 132 includes a communication-enabled diffusiondevice that diffuses scent solution(s) from scent vial(s) installed inthe scent dispenser 132. The scent dispenser 132 may include wirelesstransceivers configured to communicate with other devices within range,such as other scent dispenser(s) 132 and/or access point(s) 120. In someembodiments, the diffusion device nebulizes the scent solution into theair of the surrounding environment to diffuse the scent. The structure,acts, and/or functionality of the scent dispenser 132 is discussedfurther below.

The access point 120 connects to the set of scent dispensers 132installed on the premises 140, as shown by the signal lines 134 a...134n, and exchanges data sent between the scent dispensers 132 and themobile device(s) 106 and/or the dispenser management server 150 (e.g.,via the signal line 138).

The dispenser management application 160 operable by the dispensermanagement server 150 can receive operational data from the scentdispensers 132 in association with the premises 140, room 142, user(s)112, and/or scent vials (e.g., see FIG. 2C) with which they areassociated. The dispenser management application can receive managementrequests and geolocation data from mobile devices of the user(s) 112 inassociation with the scent dispenser(s) 132 that are registered to theuser(s) in the system 100. The management requests may includeregistration data requesting to register a scent dispenser 132 with auser’s 112 account, a particular premises, and/or a room within thepremises; scheduling data requesting to schedule dispensation ofscent(s), from scent dispenser 132 or a set of two or more scentdispenser(s) 132, for particular timeframe(s) within a particular roomof a premises; operational data instructing to activate or deactivate ascent dispenser 132 and/or specifying which scent solution to activateand/or deactivate; geolocation data indicating a current location of auser, etc. The scheduling data may include a reoccurring schedule thatrepeats on certain days and/or times of day, and may specify which scentsolution(s) should be dispensed at which times.

In some embodiments, the dispenser management application 160 maymaintain the device states, scent allocations, users, and schedules ofthe scent dispensers 132. The dispenser management application 160 maymake device function calls to command/control the scent dispensers 132(e.g., by sending state settings), and may receive and log publishedevents (heartbeat, alerts, data, etc.) received from the scentdispensers 132 in the data store 170. Example events may include, butare not limited to:

Description Event Name (string) Event Data (string) Device online“spark/status” online Device flash started “spark/flash/status” startedDevice flash successful “spark/flash/status” success Heartbeat every ##minutes “msg” See below table. Bay 1 Empty “msg” bay1_empty Bay 2 Empty“msg” bay2_empty

Further, an example heartbeat event be associated with a timestamp andmay include a delimited string reflecting various operation aspects of ascent dispenser 132. One such non-limiting example string may be

“1,2,99999999,200,200,100,100,100,255:255:255,100,100,200,200”, wherethe delimited values may have the following meaning:

Description Short Description Type (int, double, string) Range/unitExample max char Package Version # version integer 1-9 1, Heatingelement state heaterState integer 0-2 (0 = none enabled, 1 = heater 1enabled, 2 = heater 2 enabled) 2, Heating element duration (time heaterhas been active) (ms) heaterDuration integer 1-99999999 (ms) 99999999,Slot/Bay 1 temperature bayTemp1 double -50 - 200 200, Slot/Bay 2temperature bayTemp2 double -50 - 200 200, Slot/Bay 1 volume bayVol1integer 0-100 100, Slot/Bay 2 volume bayVol2 integer 0-100 100, Ambientlight ambientLight integer 0-100 100, Mood light state (rgb) mLStatestring 255:255:255 255:255:255, Slot/Bay 1 fragrance identifier bayFID1integer 0-999 999, Slot/Bay 2 fragrance identifier bayFID2 integer 0-999999, Slot/Bay 1 fragrance target temperature bayTempTar1 integer 0-100200 Slot/Bay 2 fragrance target temperature bayTempTar2 integer 0-100200,

In the above table, temperature is in Celsius, length is in millimeters(mm), duration is in milliseconds (ms), and time zone is any particulartime zone (e.g., Mountain Time Zone (UTC -07:00)). Further, a fragranceidentifier is a unique ID that corresponds to a specific type of scentsolution, and a fragrance temperature is a temperature or range that aspecific scent solution is heated to. Additionally, the scent dispenser132 may be placed in various different operation states, such as but notlimited to listening mode – for onboarding new credentials, safe mode –for development, DFU mode – for development, and connected – for normaloperation.

In some embodiments, the scent dispenser 132 may support variousfunctions, calls for which may originate from other devices of thesystem 100, such as the dispenser management application 160. Twonon-limiting example functions may include command and tune:

-   int command(String operation); and-   int tune(String operation),

where the tune function may use the format “TunableParameter,[value]”for the operation parameter. In this example, [value] is a positiveinteger. The scent dispenser 132 may respond with a ReturnCode if therequest was received, such as:

    enum ReturnCode {       PURA_FAILURE = 0,       PURA_SUCCESS = 1 };

Non-limiting example acts that may be performed using the abovefunctions may include:

Description Function String operation Enables bay 1 heater commandenableHeaterBay1 Enables bay 2 heater command enableHeaterBay2 Disablesbay 1 heater command disableHeaterBay1 Disables bay 1 heater commanddisableHeaterBay2 Sets mood light RGB tune mLRGB,[value]:[value]:[value]Sets mood light activation threshold tune mLThreshold,[value] Sets bayfragrance identifier and temperature (*C) TunebaySet,[value1],[value2],[value3] Value 1: bay # (1 or 2) Value 2:fragrance identifier Value 3: fragrance target temperature

Users may register with the scent service embodied by the dispensermanagement application 160, which enables them to remotely configure andinteract with their respective scent dispensation installations 158, andto receive notifications automatically as state changes are detected bytheir scent dispensation installations 158.

The dispenser management server 150 includes a data store 170 storingvarious types of data used by the dispenser management application 160.Example data types include dispenser data 172, user data 174, fragrancedata 176, usage data 178, premises data 180, and analytics data 182. Thedispenser data 172 may include entries for the scent dispensers 132 inthe system 100. A given entry may include a unique identifier for thecorresponding scent dispenser, a firmware version, an operational statusindicator (e.g., on, off, etc.), a schedule including which day(s) ofthe week and/or times of day the scent dispenser should be operating,which scent solution(s) should be dispensed during the scheduledtimeframe(s), whether/which color light should be illuminated, the useridentifier(s) with which the scent dispenser is registered, etc.

The user data 174 may include entries for the users 112 of the system100. A given entry may include a unique identifier for the user, contactinformation for the user (e.g., address, phone number, electronicaddress (e.g., email)), payment information, scent subscriptioninformation specifying which reoccurring scent vials should be shippedto the user, historical scent vial purchase information, etc.

The fragrance data 176 may include entries for the different scentsolutions that are supported by the system 100. An example entry mayinclude a unique identifier for a given scent, a scent name, a scentdescription, a list of ingredients that comprise the scent’scomposition, an indication of the strength of a scent, room types forwhich to suggest the scent, etc.

The usage data 178 may include logged usage statistics received from thescent dispensers 132 deployed in the system 100. Example usagestatistics may include hours of operation, which scent solutions wheredispensed during those hours of operation, thus reflecting the time ofday scent solutions were utilized, the amount of scent solutions thatwere dispensed as measured by vial sensors included in the scentdispensers 132, the rate at which the scent solutions were dispensed,etc. The usage statistics for a given scent dispenser 132 may bespecifically associated with the user associated with the usage and/or aroom of a premises in which the scent dispenser 132 is installed.

Further, the fragrance data 176 may include vial data including uniqueidentifiers for each scent vial produced and registered for use in thesystem 100. The vial data may reflect the installation status of a vial,the unique identifier of the scent solution contained by the vial, andthe fill level of the vial, an eligibility status, etc. For instance,the vial data for a particular vial may indicate whether the vial is newand has not yet been installed, that the vial is currently installed buthas not yet been depleted of its solution, and that the vial wasdepleted of its solution and is no longer eligible for use.

The premises data 180 may include entries for different premises 140 inwhich scents dispensers 132 are installed. The premises data 180 mayinclude different rooms 142 for the premises 140, and may indicate inwhich specific rooms 140 the scent dispensers 132 are installed. Examplepremises data may include unique identifiers for each of the premises,room names for each of the rooms of a given premises (e.g., which may becustomized by the user), the dimensions of the rooms of the premises, anindication of which scent dispensers 132 are installed in which rooms ofa given premises, for example, using the unique identifiers of the scentdispensers 132, etc., an indication of which unique user identifiers areassociated with which unique premises identifiers, etc.

The analytics data 182 may include data produced by the dispensermanagement application 160 the data stored in the data store 170. Forinstance, data from the scent dispensers belonging to users 112 may beaggregated by the server in the data store 170 and then analyzed togenerate analytics. These analytics can be used by the manufacturer toimprove the product, the user to evaluate his/her usage, and the scentsolution producers to learn more about their users, the users’ habitsand preferences, their products, etc.

Example analytics data may reflect scent preferences, such as whichscents consumers use most often (e.g., based on the usage data 178determined by a vial sensor), scent preferences by room type of thepremises (e.g. floral for bathrooms, edible scents for kitchens, etc.)(e.g., based on the correlation between the fragrance data 176 and thepremises data 180), which scents consumers are repurchasing the most(based on user data 174), whether or not consumers are mixing scents inspecific rooms (e.g., based on the correlation between the fragrancedata 176, the usage data 178, and the premises data 180), scentpreferences by season (based on time/data coded usage data 178),preferences for strength of a scent (light vs. strong fragrance) anddoes that differ by room (e.g., based on the correlation between thefragrance data 176, the usage data 178, and the premises data 180),whether consumer scent preferences evolve over time (e.g., based on theusage data 178), preference for classic vs. novelty scents (e.g., basedon the usage data 178 and the fragrance data 176 that tags each scent asclassic or novelty), etc.

Example analytics data may reflect scent dispensation behaviors, such ashow often users use their scent dispensers 132 (e.g., based on the usagedata 178), is the use continuous or as needed (e.g., based on the usagedata 178), how long is the continuous use (e.g., several hours, e.g.,several days, etc., based on the usage data 178), how long does it takefor consumers to change out a cartridge/refill (e.g., usage datareflects an empty vial stayed in the scent diffuser 132 for a certaintimeframe, which can be averaged over many, or all users (e.g.,generally, for that fragrance type, etc.)), how often are consumerspurchasing refills (e.g., based on the user data 174 reflecting purchasehistory), preferred rooms for using scent dispenser 132 (e.g., based onthe correlation between the usage data 178 and the premises data 180),use of scent dispensers 132 when users 112 are in vs. out of thepremises 140 (e.g., based on the correlation between the users’ 112 userdata 174 and the usage data 178), etc.

Example demographics data may reflect behaviors and preferences bydifferent demographic groups. User data may reflect a user’s gender,age, income, race/ethnicity, number of children in the home, number ofpets in the home, region, settlement-type (urban, rural, suburban,etc.), premises type (single family home, apartment, condo, townhouse,small business, large business, hotel, bed and breakfast, warehouse,restaurant, etc.), personal or business, etc. Using the user data, anyof the other data or combinations thereof may be segmented to determinewhich groups may be more or less predisposed to scent dispensation, andhow different factors affect the level of scent dispensation by aparticular group.

The data stored by the data store 170 may be correlated using variouscommon keys, such as unique identifiers (e.g., user identifiers, roomidentifiers, fragrance identifiers, scent dispenser identifiers, vialidentifiers, room identifiers, premises identifiers, etc.), which allowthe dispenser management application 160 to generate and provide richanalytics. Example graphical representations that may be rendered fordisplay on a computing device 106 of a user 112 are depicted in FIGS.26-27B. In particular, FIG. 26 illustrates an example graphical userinterface 2600 including a digital data visualization 2604 showing usagestatistics for different scent solutions (e.g., lavender dream, dragonberry, green tea citrus, autumn café, golden dahlia).

In some embodiments, the statistical data used to generate the digitaldata visualization 2604 is received from a multiplicity of scentdispensers 132 installed in different premises in the system. The vialsensors of the scent dispensers 132 detect the changes in the fluidlevels of the vials as the solutions from the vials are diffused intothe air of the respective premises 140. The controllers of the scentdispensers 132 receive the data reflecting the changing fluid levels andtransmit that data to the dispenser management server 150, which in turnstores the data as usage data 178 in the data store 170 in associationwith the scent/fragrance ID to which the data corresponds. As a result,the usage data 178 reflects the amount of each scent solution that isconsumed over time for each scent dispenser 132 relative to the user ID,the premises ID, the room ID, scent dispenser 132 ID, the vial IDassociated with that particular scent solution (e.g. which isidentifiable as discussed elsewhere herein).

FIGS. 27A and 27B are graphical representations of further graphicaluser interface 2700 for displaying and providing user interaction withscent analytics. As shown, the graphical user interface 2700 includesusage statistics 2706 for a particular scent solution (e.g., lavenderdream), including segmentation by gender, age, room type,settlement-type. The statistics 2706 include information on how manytimes that particular scent solution was reordered before switching toanother scent solution (e.g., refilled in this case means the vial wasswitched out for a new vial in the users’ 112 scent dispensers 132), aswell as the average hours the scent solution was used each day by theusers 112 who have the scent solution installed in their scentdispensers 132. The graphical user interface 2700 includes acorresponding set of digital data visualizations 2704 that correspond tothe usage statistics, as shown in FIG. 27B.

FIG. 1B is a block diagram illustrating an example scent dispenser,which is depicted as including a power supply (PS) 184, a set of sensors186, a controller 188, an interface 190, output device(s) 192, dispenserfirmware 194, heating element(s) 196, and any number of vials 205a...205n (individually or collectively also referred to as simply 205).The components 184, 186, 188, 190, 192, and 196 are communicativelycoupled via a communications bus 198. The controller 188 may include anon-transitory memory device, or may be coupled to a non-transitorymemory device also coupled for communication via the bus 198. Thenon-transitory memory device may store software that speciallyconfigures the controller, such as the dispenser firmware 194. The PS184 may be any AC and/or DC power supply for powering the scentdispenser 132. The controller 188 is a microchip that controls theconstituent electronics (e.g., sensor(s) 186, output device(s) 192,interface 190, heating element(s) 196, etc.) of the scent dispenser. Anon-limiting example of the controller 188 may include an ARM-basedmicrocontroller, such as one manufactured by Mouser Electronics under PNP1 REEL, although it should be understood that other chip architecturesare also applicable, that the controller 328 may be combined with otherprocessors, and/or that numerous other variations are possible,contemplated, and applicable.

The set of sensor(s) 186 may include a vial sensor for sensing the filllevel of the vial(s) 250 installed in the scent dispenser 132, opticalsensor(s) for detecting an identity of vial(s) installed in the scentdispenser 132, temperature sensors (e.g., thermocouples, etc.) forsensing the temperature of the heating element(s) 196, ambient lightsensor to detect a light level in a surrounding environment (e.g.,room), and/or a motion sensor to detect motion in the surroundingenvironment, etc.

In some embodiments, the sensors 186 may include a temperature baysensor for each heating element 196 (e.g., that may measure temperaturesranging from (-50 to 200° C.), the vial sensor 300 (e.g., see FIG. 3A),an ambient light sensor, etc.). The heating element 196 may beconfigured to heat to any suitable temperature sufficient to diffuse ascent solution contained in a corresponding vial 250, a non-limitingexample of which may be 65° C., and the temperature bay sensor 186 maybe mounted on or adjacent to, or embedded in, the heating element 196 tomeasure the temperature of the heating element 196 and provide feedbackto the controller 188, which may cyclically heat the heating element 196based on the feedback to maintain a constant or substantially constanttemperature during diffusion (as set in the state settings).

The sensors 186 include a transceiver having a wireless interfaceconfigured to communicate with the devices coupled to the network 102,such as the access point 120, the dispenser management server 150,and/or other components of the network 102 using standard communicationprotocols, such as Internet protocols. Further, the transceiver may beconfigured to wirelessly transmit data via a meshwork network made up ofa plurality of scent dispensers 132 and/or other devices, such as theaccess point 120 or a mobile device 106. By way of further example, thetransceiver may transmit data to the access point 120 to which it islinked using a protocol compliant with IEEE 802.15, such as Zigbee®,Z-Wave®, Bluetooth®, or another suitable standard. Additionally oralternatively, one or more of the scent dispenser(s) 132 and/or theaccess point 120 of an installation 158 may be wired for directcommunication and the wired components may exchange data using wireddata communication protocols. Further embodiments are also possible andcontemplated. In some embodiments, the transceiver may be embedded inthe controller 188 or may be a component distinct from the controllerand coupled to the controller 188 via the bus 198.

The output device(s) 192 may include light sources and/or audioreproduction devices, although further suitable output devices are alsocontemplated and applicable. The light sources and/or audio reproductiondevices may be controlled to produce output consistent with a scentbeing emitted by the scent dispenser (e.g., a low, soothing light andmusic may be output in conjunction with a relaxing scent being emitted).

Returning to FIG. 1A, the client device(s) 106 (also referred toindividually and collectively as 106) are computing devices having dataprocessing and communication capabilities. In some embodiments, a clientdevice 106 may include a processor (e.g., virtual, physical, etc.), amemory, a power source, a network interface, and/or other softwareand/or hardware components, such as a display, graphics processor,wireless transceivers, keyboard, camera, sensors, firmware, operatingsystems, drivers, various physical connection interfaces (e.g., USB,HDMI, etc.).

The client devices 106 may couple to and communicate with one anotherand the other entities of the system 100 via the network 102 using awireless and/or wired connection. Examples of client devices 106 mayinclude, but are not limited to, mobile phones (e.g., feature phones,smart phones, etc.), tablets, smartwatches or other smart wearables,laptops, desktops, netbooks, server appliances, servers, virtualmachines, TVs, set-top boxes, media streaming devices, portable mediaplayers, navigation devices, personal digital assistants, etc. Inaddition, while a single client device 106 is depicted in FIG. 1 , itshould be understood that any number of client devices 106 may beincluded.

As shown, the client device 106 may include a scent application 108,which allows the user to set scent dispenser 132 settings, turn scentdispensers 132 on and off, purchase vials for the scent dispenser 132,set up a scent dispenser 132, register an account, set up a premises andthe rooms of the premises, associate a scent dispenser 132 with aparticular room of the premises, view analytics reflecting the user’shistorical use of his/her scent dispenser(s) 132, enable user profilesto use and setup scent profiles for the scent dispenser(s) installed inthe premises, set a profile hierarchy (e.g., set which user profile(s)is/are the dominant user profile), etc.

The client device 106 may store the scent application 108 innon-transitory memory, retrieve the scent application 108 from memory,and execute instructions comprising the scent application 108. The scentapplication 108, when executed by a processor of the client device 106,configures the processor of the client device 106 to carry out the actsand functionality described herein. In some embodiments, the scentapplication 108 may render and display various interfaces for carryingout the functionality described herein, such as but not limited to thosedepicted in FIGS. 14A-20B.

In particular, FIGS. 14A-14H are graphical representations of userinterfaces for setting up a scent dispenser 132. For instance, FIGS. 14Aand 14B depict the user interface 1400 for logging into and/orregistering an account with the scent service. The user may enterhis/her credentials (e.g., email and password) in the fields 1402 or1406, may select corresponding interface elements (e.g., sign in or signup) to submit the credentials depending on whether the user is logginginto an existing account or creating a new account. Upon submission ofthe form fields, the scent application 108 may transmit the credentialsto the dispenser management application 160 and authenticate instance ofthe scent application 108.

Upon receiving a response from the dispenser management application 160that the authentication is successful, the scent application 108 mayproceed to display the user interface 1408 depicted in FIG. 14C, whichincludes a summary of the steps for setting up a scent dispenser 132 anda user interface element 1410 for beginning the setup process, which isselectable by the user. Upon following the instructions (e.g., pluggingin the scent dispenser 132), and selecting the element 1410, the scentapplication 108 displays user interface 1412, which includesinstructions prompting the user to connect his/her user device 106(e.g., mobile phone) to a wireless network broadcasted by the scentdispenser 132. An unregistered scent dispenser 132, when first pluggedinto an electrical socket, proceeds through a boot sequence of thedefault firmware stored in the memory of the scent dispenser 132. Aspart of the boot sequence, the firmware determines that the scentdispenser has not yet been initialized and proceeds to broadcast awireless network via which the user connects his/her user device and theuser can configure the scent dispenser 132.

In some embodiments, when a scent dispenser 132 is booted, it registersits functions with the dispenser management application 160, and mayresume the device’s last previously known state. If the state is unknownthe heating elements 196 may be are disabled. In some embodiments, ifthe state is different from what the controller 188 may programmed toexpect (e.g., a scent volume has changed significantly), an alert may bepublished and the heating elements 196 may be disabled. In someembodiments, when the scent solution of a vial is depleted (e.g.,drained to the lowest detectable level) the heating element 196 may bedisabled and an event may be published to the dispenser managementapplication 160, which may in turn, send a notification to the clientdevice 106 of that user (which may be registered in the usage data forthe user of that scent dispenser 132) to notify the user that the scenthas run out and is no longer being diffused, as well as provide anoption for repurchase.

As shown in FIG. 14D, the user may select the network broadcasted by thescent dispenser 132 using user selectable element 1414 of the userinterface 1412, and upon successfully connecting to the network, mayproceed to configure the scent dispenser 132. In FIG. 14E, the userinterface 1416 includes a list of user selectable networks accessible inthe location which the user stands and is presumably associated with thepremises in which the scent dispenser 132 is installed. Upon selectingone of the networks from the list 1418, the scent application 108displays user interface 1420, which includes a set of user interactableelements such as a password entry field and a save button. Upon enteringthe password and selecting save, the scent application 108 transmitsdata describing the selected wireless network and password to the scentdispenser 132 via the wireless network broadcasted by the scentdispenser 132, and the firmware stores the data for that wirelessnetwork in the memory of the scent dispenser 132, the proceeds toconnect the scent dispenser 132 to that selected wireless network. Uponsuccessfully connecting to the network, the firmware may run otherchecks such as verifying that the scent dispenser 132 can connect to thedispenser management server 150 via the network, and can register thatdispenser 132 to the user. The dispenser management application 160 mayreceive the configuration information entered via the interfacesdepicted in FIGS. 14A-14E and may store that information as user data174 in the data store 170. The user interface 1424 depicted in FIG. 14Gincludes graphical user interface elements showing the completed and yetto be completed steps involved in the configuration. The user interface1426 depicted in FIG. 14H includes information confirming successfulregistration of the scent dispenser 132, and includes a user selectableinterface element 1430 for installing one or more scent vials in thescent dispenser 132.

FIGS. 15A-15H are graphical representations of user interfaces forconfiguring vial settings of a scent dispenser. For example, FIG. 15Adepicts a user interface 1500 including a set of user selectableinterface elements for user account settings. For example, a user mayselect to disable all schedules and manually turn on and off the scentdispensers 132 registered with the user’s account using the scentapplication 108. Alternatively, the user may select to enable theschedules (which may be configured using other interfaces, such as thosedescribed elsewhere herein). The user may also select to add a new scentdispenser 132, add a vial 250 to a scent dispenser 132, replace a vial250 with another vial 250 in the scent dispenser 132, and enable ageofencing option as described elsewhere herein. Upon changing the useraccount settings, the scent application 108 may transmit user datareflecting the changes to the dispenser management server 150, and uponreceipt thereof, the dispenser management application 160 may update theuser data associated with the user to reflect the revised settings. Thesettings associated with the user and his/her scent dispenser(s) 132 mayalso be referred to herein as a user profile, and may be stored as userdata 174. The scent vial configuration (e.g., which fragrance typesand/or specific vials are installed in a given scent dispenser 132 orset of scent dispenser(s) 132) may also be referred to herein as a scentprofile of that/those scent dispenser(s) 132, and may be stored asdispenser data 172.

FIG. 15B depicts a user interface 1504 displayed by the scentapplication 108 that includes user configurable interface elements 1506for revising the user’s personal information and/or account type, anduser configurable interface elements 1508 for inputting address andpayment information.

FIG. 15C depicts a user interface 1510 displayed by the scentapplication 108 for installing a scent vial 250 into a first slot of aselected scent dispenser 132 registered to the user. The user interface1510 instructs the user to insert the scent vial 250 into the first slot(e.g., slot labeled 1, slot on left, etc.), and upon doing so, selectthe user selectable interface element 1514 to continue the installationprocess. Next, the scent application 108 displays user interface 1516,as depicted in FIG. 15D, which includes a user selectable list 1518 ofavailable scents and requests the user to select which scent the userinstalled into the first slot. Upon confirmation of the type of scentthe user selected by selecting the user interface element 1520configured for confirming the selection (e.g., save and continue), thescent application 108 transmits the installation information to thedispenser management application 160, which then stores the scentdispenser 132 information in the data store 170 (e.g., as dispenser data172, and user data 174, etc.) in association with the user’s user ID andthe scent dispenser’s 132 device ID.

FIGS. 15E and 15F depict user interfaces 1522 and 1528 for installingadditional vial(s) in the scent dispenser 132 (e.g., in the secondslot). The content and the functionality of the interfaces 1522 and 1528are substantially similar to those described with respect to FIGS. 15Cand 15D and will not be repeated here. It is noted that, onceinstallation is complete and the second vial type is saved, the scentapplication 108 may transmit the installation information to thedispenser management application 160 for storage in a mannersubstantially similar to that described with respect to FIGS. 15C and15D.

FIG. 15G depicts a user interface 1534 for associating the scentdispenser 132, and thus the scent types installed in the scent dispenser132, and in some cases, the specific identities of the first vial 250and/or second vial 250, with a particular room of the premises. Theinterface 1534 may include a user selectable list 1536 of rooms as wellas a field for entering a custom room description for the room that theuser selected from the list 1536. Upon selecting interface element 1538(e.g., save and continue), the scent application 108 may transmitinstallation data reflecting the room of the premises in which the scentdispenser 132 is installed. The dispenser management application 160 mayreceive and store this data in the data store 170 (e.g., as premisesdata 180, etc.) in association with the scent dispenser ID, the premisesID, and/or the room ID, etc.

FIG. 15H depicts a user interface 1540 to confirm that the installationprocess for installing the vial(s) in the scent dispenser 132 iscomplete, which includes a list of information about the installation,such as the room in which the scent dispenser 132 is installed, andidentify information about the scent installed in the scent dispenser132. The user may exit the installation process by selecting the userinterface element 1542.

FIGS. 16A-16E are graphical representations of user interfaces forscheduling scent dispensation for one or more rooms. FIGS. 16A-16Cdepict the user interface 1600, which includes a set of user interfaceelements 1602 and 1604 that are user configurable to set a schedule fora scent dispenser 132. In particular, using the set of user interfaceelements 1602 and 1604, the user may activate the device, and select astart and end time for scent dispensation. Further, the user may adjustthe scent intensity and select whether to illuminate the light of thesensor during scent dispensation, and select to add additional scentschedules to the device, such as a schedule of different time and/or dayfor an alternative scent, etc. While not depicted, the set of userinterface elements 1602 may also include a day calendar from which theuser may select particular days of the month in which to schedule thescent dispensation. The user may select a one-time schedule orreoccurring schedule using the interface elements 1602 and 1604.

FIG. 16D depicts a user interface 1608 that includes a set of userinterface elements 1610 in which the user may customize the color of thelight that may be output by the scent dispenser 132 during scentdispensation. In some embodiments, the user interface 1608 may includean automatically selected color that is determined to correspond withthe scent scheduled to be dispensed (e.g., relaxing bath). In someembodiments, the user may manually select and/or customize which colorshould be illuminated, or select from a list of previously selectedcolors that the scent application 108 stored or retained in memory. FIG.16E depicts a user interface 1612 for selecting a custom color for thelight using user interface elements 1614 (e.g., intensity selector, hueselector, etc.). Upon configuring the schedule and light settings, thescent application 108 may transmit the schedule data reflecting thesettings to the dispenser management application 160, which may storethe settings in the data store 170 (e.g., as user data, dispenser data,etc.) in association with the user’s user ID, the scent dispenser 132ID, etc.

FIG. 17 is a graphical representation of a user interface 1700 forviewing vial properties of an installed vial. As shown, the vialdepicted in the interface 1700 has a 45% capacity. This fill level maybe determined by the vial sensor of the scent dispenser 132 configuredto detect fill level of the vial. The controller of the scent dispenser132 may transmit the fill level data received from the vial sensor tothe dispenser management application 160 for processing and/or storagein the data store 170 as usage data 178 in association with the scentdispenser 132 ID, the user ID associated with the scent dispenser 132,etc. The user interface 1700 includes user selectable options 1702 forsaving that scent type to the user’s account (e.g., as reflected by theuser data 174 associated with the user ID of that user) and/or orderingreplacement/refill vial 250 from an online marketplace hosted by thedispenser management application 160 and/or another e-commerce server orservice coupled to the network 102.

FIGS. 18A-18M are graphical representations of user interfaces ofelectronic marketplace for (re)ordering vials. FIG. 18A depicts a userinterface 1800 including interface elements 1802 selectable for viewinginformation about scents currently installed in the scent dispenser(s)132 of the user, viewing all available scent types, and viewing scenttypes by various categories such as room type.

FIG. 18B depicts a user interface 1806 including user interface elements1808 selectable for viewing scent types by room type. For instance, uponselecting a bedroom room type, the scent application 108 may display theuser interface 1810 depicted in FIG. 18C, which includes a list 1812with which the user may interact to view information about differentscent types that are recommended for use in the bedroom.

FIG. 18D depicts a user interface 1814 including user selectableinterface elements 1816 for viewing scent types by category or theme.For instance, the user may select to view different scents recommendedfor relaxation, such as those depicted in FIG. 18E, which displays theuser interface 1818 including a user-selectable list 1820 of scents.FIG. 18F depicts a user interface 1822 that includes a user selectablelist 1824 of all available scent types. The user may select a scent fromthe various lists depicted in the forgoing figures to view additionalinformation about that scent. An example interface 1826 displayingdetailed information about a scent is depicted in FIG. 18G. As shown,the user may review information about the scent and use the userselectable interface elements 1828 to either save the scent to theuser’s 112 account for later purchase, or to purchase immediately.

In some embodiments, the scent service embodied by the dispensermanagement application 160 may provide a subscription service to theuser in which a certain number of scent vials are automatically shippedto the user (e.g., monthly). The user, using the interfaces depicted inFIGS. 18A-18M, browses and selects the scent vials 250 to add to anupcoming shipment and/or future shipments. When the time comes, afulfillment center associated with the scent service automaticallyfulfills the items selected by the user for purchase. For instance, asdepicted in FIG. 18G, the interface 1826 includes a user-selectableoption for the user to add the scent vial 250 to the next shipment(e.g., add to box.). Upon selection of the interface element, the scentapplication 108 may transmit order data reflecting the addition of thescent vial 250 to the next shipment, and the dispenser managementapplication 160 may store the order information as user data 174 inassociation with the user, which may be transmitted to a fulfillmentcenter system to facilitate fulfillment of the order.

FIG. 18H depicts a user interface 1830 reflecting scent vials that theuser has saved to his/her profile for later ordering. Upon selection ofone or more of the user selectable interface elements 1832 (e.g., addbuttons), corresponding scent vials may be selected forpurchase/shipment.

FIGS. 18 l and 18J depict a user interface 1834, which includes userinterface elements 1836 reflecting the items selected to be included inthe user’s next shipment, as well as interface elements 1838 includinginformation reflecting when the shipment will occur.

FIG. 18K depicts a user interface 1842 including user interface elements1844 reflecting the current shipment confirmation and previous shipmentconfirmations. FIG. 18L depicts a user interface 1846 including userinterface elements 1848 providing the user the option to add additionalitems to a pending shipment, a new shipment, or a subsequentsubscription service shipment. FIG. 18M depicts a user interface 1850including user interface elements 1848 completing a purchase transactionfor purchasing scent vials.

FIGS. 19A-19F are graphical representations of user interfaces forviewing and configuring room, schedule, and dispenser settings. FIG. 19Aincludes information about which scent dispensers 132 are currently onand which scent dispensers 132 are scheduled to turn on. The informationalso reflects the scent being dispensed or scheduled to be dispensed bythe corresponding scent dispensers 132. The user interface 1900 includesuser-selectable interface elements 1902 for modifying the settings ofthe currently active scent dispensers 132, as well as user-selectableinterface elements 1904 for modifying the settings of the currentlydormant scent dispensers 132 and the scent dispensers 132 which areturned off. As the state of the scent dispensers 132 change over time,the dispenser management application 160 may send refreshed operationaldata for the scent dispensers to the scent application 108, and thescent application 108 may refresh interfaces described herein to reflectthe current operational state and/or configurations of the scentdispensers 132. Information about each of the scent dispensers 132registered to the user, including which scents are installed in thescent dispensers 132 and the rooms that the scent dispensers 32 areinstalled in, can be retrieved by the scent application 108 from thedispenser management application 160. Correspondingly, the dispensermanagement application 160 may retrieve this information from the datastore 170, as described elsewhere herein.

FIG. 19B depicts a user interface 1906 for viewing the details of aparticular room (e.g., Lukas’ bedroom). The scent application 108 maydisplay the interface 1906 responsive to the selection of a room/scentdispenser 132 in the interface 1900 depicted in FIG. 19A. The userinterface 1906 may include the current 1908 and upcoming schedules 1910for the scent dispenser(s) 132 installed in Lukas’ bedroom. For example,currently a scent dispenser 132 in Luka’s bedroom is actively dispensingrelaxing bath (until 7PM), and is scheduled to dispense a calming scent(between 7PM and 10PM). A user may select any of the listed schedules,and modify that schedule and/or turn off the scent dispenser 132 using acorresponding interface, as discussed elsewhere herein.

FIG. 19C depicts a user interface 1912 including a user selectableinterface toggle 1914 for toggling the scent dispenser 132 in aparticular room (e.g., guestroom) on and off. In this case, turning thescent dispenser 132 off/inactive overrides the schedules defined forthat scent dispenser 132. Using the user selectable interface elements1916, the user may select any of the scheduled times for modification,and responsive thereto, the scent application 108 may display a scheduleediting interface, as discussed elsewhere herein.

FIG. 19D depicts a user interface 1918 including user-selectableinterface elements 1920 for editing different aspects of the scentschedule, such as the time the scent dispensation is scheduled to occur,whether or not to illuminate a light, and the intensity of the scentdispensation, as discussed elsewhere herein.

The user interface 1922 in FIG. 19E, which may be displayed responsiveto the selection by the user to edit the light settings in the userinterface 1918, provides the user options 1924 for configuring theintensity and hue of the light to be illuminated during the scheduledtime.

FIG. 19F depicts a user interface 1926 including a user configurableinterface element 1928 for adjusting scent dispensation intensity duringthe scheduled time. For example, the user may use the slider to adjustthe intensity up and down. The intensity setting, as with any other ofthe settings described with reference to the interfaces, may betransmitted to the dispenser management application 160 and stored inthe data store 170 and/or transmitted to the scent dispenser 132 asoperational settings.

FIG. 20A is a graphical representation of a user interface 1930including a notification prompting the user to install a new orreplacement vial. The notification may include a user selectableinterface element 1932 for installing a new scent vial. Responsive tothe selection of the element 1932, the scent application 108 may providethe user with instructions on how to swap out the old/empty vial with anew vial 250 and/or provide the user with options to purchase additionalscent vials 250.

FIG. 20B is a graphical representation of a user interface 1934 fordisabling geolocation-based control of scent dispensation. In someembodiments, responsive to the user, and the user’s mobile device 106,leaving the premises that is registered to the user (e.g., as reflectedby geofence settings stored as user data 174 in the data store 170and/or the memory of the mobile device 106), the scent application 108may display the user interface 1934 notifying the user that all of thescent dispensers 132 on the premises were automatically turned off/madeinactive because the user was not present at the premises. The userinterface 1934 further provides the user selectable interface element1936 for disabling the automatic turning off of the scent dispensers 132upon leaving the premises. Upon selecting the user interface element1936, the scent application 108 transmits updated setting to thedispenser management application 160 instructing the sensor managementapplication 160 to update the user’s account to reflect not inactivatingthe scent dispensers 132 when the user leaves the premises.

Returning to FIG. 1 , the dispenser management server 150 may includeone or more computing devices having data processing, storing, andcommunication capabilities. For example, the server 150 may include oneor more hardware servers, virtual servers, server arrays, storagedevices and/or systems, etc., and/or may be centralized ordistributed/cloud-based. In some embodiments, the server 150 may includeone or more virtual servers, which operate in a host server environmentand access the physical hardware of the host server including, forexample, a processor, memory, storage, network interfaces, etc., via anabstraction layer (e.g., a virtual machine manager).

While not depicted, the server 150 may include a (physical, virtual,etc.) processor, a non-transitory memory, a network interface, and adata store 170, which may be communicatively coupled by a communicationsbus. Similarly, the client device 106 may include a physical processor,a non-transitory memory, a network interface, a display, an inputdevice, a sensor, and a capture device. It should be understood that theserver and the client device may take other forms and include additionalor fewer components without departing from the scope of the presentdisclosure.

Software operating on the server 150 (e.g., the dispenser managementapplication 160, an operating system, device drivers, etc.) maycooperate and communicate via a software communication mechanismimplemented in association with a server bus. The software communicationmechanism can include and/or facilitate, for example, inter-processcommunication, local function or procedure calls, remote procedurecalls, an object broker (e.g., CORBA), direct socket communication(e.g., TCP/IP sockets) among software modules, UDP broadcasts andreceipts, HTTP connections, etc. Further, any or all of thecommunication could be secure (e.g., SSH, HTTPS, etc.).

As shown, the server 150 may include a dispenser management application160 embodying a remotely accessible scent service. The dispensermanagement application 160 may send data to and receive data from theother entities of the system including the controllers 188 and/or 328,the mobile device(s) 106, etc. The dispenser management application 160may be configured to store and retrieve data from one or moreinformation sources, such as the data store 170. In addition, while asingle server 150 is depicted in FIG. 1 , it should be understood thatone or more servers 150 may be included.

In some embodiments, the dispenser firmware 194, the scent application108, the dispenser management application 160, etc., may require usersto be registered to access the acts and/or functionality provided bythem. For example, to access various acts and/or functionality providedby the scent application 108, dispenser management application 160,and/or scent dispensers 132, these components may require a user toauthenticate his/her identity (e.g., by confirming a valid electronicaddress). In some instances, these entities 108, 132, 150, etc., mayinteract with a federated identity server (not shown) toregister/authenticate users. Once registered, these entities 108, 132,150, etc., may require a user seeking access to authenticate byinputting credentials in an associated user interface.

FIGS. 2A-2G are various views of an example scent dispenser 132. Asshown, the scent dispenser 132 includes a housing 200 that houses thecomponents of the scent dispenser (e.g., vial coupling(s), heatingelement(s), vial sensor, etc.).

The housing 200 includes a body 202 and a detachable lid 204. Thebackside 212 of the housing includes a plug 206 that can be plugged intoa conventional outlet (e.g., 146) to power the device. The scentdispenser 132 also includes one or more electronic interfaces, such asUSB port 208, which the user can utilize to charge other devices, plugthe scent dispenser into a computer to update firmware, set settings,etc. The housing 200 may also include one or more output devices 210,such as LED(s), which are discussed further below.

As shown in FIG. 2C, the lid 204 of the dispenser 132 is removable toprovide access to one or more scent vials 250 (e.g. in this case two,although conceivably any number of scent vials can be included), whichcan be inserted into a cavity 220 exposed by the lid when removed. Inparticular, when the lid 204 is removed, it exposes an inner surface 216including a concave surface 218 that forms the cavity 220. Thelid/removable cover 204 can be (re)attached to the front side/innersurface 216 of the housing 200 to cover the opening/cavity 220 providingaccess to the vial(s) 250.

The cavity 220 includes two slots 222 (left and right from a front view)in the depicted embodiment, although it should be understood that anynumber of slots maybe included to accommodate any number of scent vials250. Each slot 222 accommodates a corresponding vial 250, which containsparticular scent solution (not depicted).

The front side/inner surface 216, which is exposed when the lid 204 isremoved, includes a (e.g., second) set of magnetic fasteners 226 thatare configured to magnetically detachably attached to a corresponding(e.g., first) set of magnetic fasteners 228 included in the removeablecover/lid 204. For instance, the lid 204 may include a set of magneticfasteners 228 on an inside surface (not shown) of the lid that abuts theinner surface 216 that engage with the set of magnetic fasteners of thebody when the lid is situated abuttingly with the front side/innersurface 216 of the housing 200 of the scent dispenser 132.

FIGS. 5A and 5B are various views of an example vial 250, although itshould be understood that the vial 250 may take other forms and havedifferent dimensions. The solution may include chemical(s) that areprocessed by the scent diffuser 132 to diffuse or nebulize it within theroom in which the scent dispenser 132 is placed. The solution in someembodiments may be a liquid perfume, an essential oil, or other suitablesolutions. In some alternative, the perfume or essential oil may becaked and the caked substrate may be heated to diffuse the scent. A vial250 may be made of any suitable material, such as plastic, metal,ceramic material, glass, etc.

In some embodiments, a vial 250 (e.g., a first vial, second vial, etc.)may include a first side 264, one or more sidewalls 266, and a secondside 288. For example, a vial 250 having a tubular sidewall may be acontinuous around a circumference. In another example, a vial 250 havinga square, triangular, rectangular, etc., cross-section (e.g., halfwaybetween the second side 268 and the first side 264) at a middle of thesidewall, may have a plurality of sidewalls that are joined along at thecorners of the cross-section. It should be understood that the vial 250may have any shape. The one or more sidewalls 266 connecting the firstside 264 to the second side 268. The first side 264, the one or moresidewalls 266, and the second side 268 collectively form an inner cavity(e.g., see FIGS. 4A-4D). The first side 264 includes an opening 262through which a solution containable in the inner cavity can bedispensed from the vial 250.

In some embodiments, the first side 264 includes a neck 258 forming theopening 262, and the sidewall(s) 266 and second side 268 form a hollowbody 256. The hollow body forms a cavity containing the scentedsolution. A wick 252 may extend from the cavity through the opening 262of the neck 258.

As shown in FIGS. 5A and 5B, in some embodiments, the vial 250 mayinclude a stopper 254 and a wick 252. The stopper 254 inserts into anopening 262 of the vial 250 and forms a seal against an inner surface ofthe neck 258. The stopper 254 includes a through-hole 251 extendingthrough a center portion of the stopper 254 from an outer surface 255 ofthe stopper to an inner surface 254 of the stopper 254. Thethrough-hole/opening 251 is formed in the stopper to allow a wickinserted into the cavity of the vial 250 to extend outwardly from thethrough-hole 251, and thus the opening 262 of the first side 264.

FIG. 2D is an exploded view of the scent dispenser 132 housing 220 withthe lid 204 removed. As shown, the scent dispenser 132 includes a backhousing portion 233 and a front housing portion 231 that are attachableusing one or more fasteners 232 (e.g., screws, snaps, etc.). The backhousing portion 233 and the front housing portion 231 collectivelyenclose and retain the electronics of the scent dispenser 132. In thedepicted example, the dispenser’s 132 electronics may a controller 188that controls the components of the scent dispenser 132. In someembodiments, the scent dispenser 132 includes multiple circuit boards(e.g., a sensor board 237, a main board 235), although it should beunderstood that the boards could be combined or further split up, etc.In the depicted embodiment, the main board 235 includes the controller188. FIGS. 21-25 are schematic diagrams of various example electronicsof the scent dispenser 132 illustrating wiring and features of theelectronics that would be readily interpretable and understandable byone having skill in the art. In particular, FIG. 21 is a schematicdiagram of an example controller 188, which includes a wirelesscommunications chip (e.g., the interface 190); FIG. 22 is a schematicdiagram of an example PS 184; FIG. 23 is a schematic diagram of anexample heating element circuit including the heating element(s) 196;FIG. 24 is a schematic diagram of an example sensor 186, such as atemperature sensor configured to sense the temperature of a heatingelement 196 and provide the temperature to the controller 188 fortemperature feedback control; FIG. 25 is a schematic diagram of anexample output device 192, such as an array of LEDs controllable by thecontroller 188 based on light settings set using the scent application108.

In FIG. 2E, a retaining mechanism 248 of the vial 250 couples with acorresponding retaining mechanism 246 included in a slot of the scentdispenser 132. In some embodiments, the vial retaining mechanism 248 mayinclude first and second vial couplings 244. The first and second vialcouplings 244 receive and detachably retain the first side 264 of thefirst and second vials 250, respectively. In some instances, the firstand second vial couplings 244 includes one more surfaces shaped toengage with and secure the neck 258 of the first side 264 of the firstand second vials 250.

As shown, the retaining mechanism 248 may be a protrusion extendingoutwardly from a surface of the vial, such as the neck or the body ofthe vial. In the specific example depicted, the protrusion extendsaround the circumference of the neck 258 of the vial 250, and theretaining mechanism 246 includes one or more coupling devices 244 thatengage with the retaining mechanism 248. In some embodiments, thecoupling devices 244 may comprise one or more fasteners formed todetachably engage with the neck of the vial. For instance, the couplingdevices 244 may include one or more clips protruding outwardly from astopping member 249 along the neck 258 of the vial 250 toward the body256 of the vial 250. The clips include protrusions protruding inwardlytoward the neck such that they engage with and hold the protrusion 260of the neck 258.

It should be understood that other variations for the retainingmechanism 248 and 246 are also possible and contemplated. For instance,the protrusion 260 may engage with corresponding channels formed in asurface of the retaining mechanism 246 into which protrusion 260 slidesinto an opposing side(s). In another example, the neck 258 includes agrove and the retaining mechanism 246 includes corresponding protrusionsor rails that mate with the grove. Numerous other variations are alsopossible and contemplated.

As illustrated in FIGS. 2F and 2G, the scent dispenser 132 may include aheating element(s) 196 to heat the solution from the vial(s) 250installed in the scent dispenser 132. In some embodiments, the wick 252passes a scented solution to the heating element 196. The heatingelement 196 diffuses the scented solution by heating the scentedsolution to the temperature level regulated by the controller 188.

An example heating element 196 may include a ceramic material (e.g.,ceramic resistor, such as a wire wound ceramic heating element). Heatingthe solution received from the vial 250 accelerates diffusion of thesolution into the surrounding air. The housing 200 may include one ormore ports 214 in the lid 204 to allow the diffused air to pass into thesurrounding environment, as shown in FIGS. 2A and 2B. The more heatapplied by the diffusion device, the stronger the evaporative rate andthus the stronger the smell that may be produced.

In some embodiments, a scent solution of a vial 250 may require acertain heating range to be diffused effectively, and the controller 188may receive specific state settings for that scent solution from thedispenser management application 160 and use those settings to controlthe temperature of the corresponding heating element 196.

In the depicted embodiment, the vial retaining mechanism 246 includeswick receiver(s) for receiving the end(s) of the wick(s) 252 of theinstalled vial(s) 250 and passing them to the heating element(s) 196.For instance, the scent dispenser 132 may include a first (e.g., left)heating element 196 situated on a side of the stopping member 249opposing a first (e.g., left) vial 250, and a second (e.g., right)heating element 196 situated on the side of the stopping member 249opposing the second (e.g., right) vial. The first heating element 196heats an end of the wick 252 extending through the wick hole 247 of thefirst wick receiver 243, and the second heating element 196 heats an endof the wick 252 extending through the wick hole 247 of the second wickreceiver 243.

A wick receiver 243 may include a stopping member having a wick hole 247extending through the stopping member 249 of the wick receiver 243. Thewick hole 247 of the wick receiver 243 receives a wick 252 extendingoutwardly from the opening of the first side 264 of the vial 250 (e.g.,see FIGS. 5A and 5B). Multiple wick receivers 243 may be included tomatch the number of vials being heated.

In some embodiments, a heating element 196 is shaped to receive and heata wick 252 of a vial 250. For example, the a heating element 196 (e.g.,first, second, etc.) may include a ring 245 b extending from a main body245 a that receives the end of the wick 252 extending through the wickhole 247 of the wick receiver 243. In some instances, a metallic heatingwire may be wound in the main body 245 a and the ring conducts the heataround the wick 252, although other variations are also possible andcontemplated.

The electronics (e.g., 235) of the scent dispenser 132 include anintensity control unit that controls the intensity of diffusion by thediffusion device. For example, the controller 188 may use pulse widthmodulation (PWM) to digitally control the (analog) power provided to aheating element 196 of the diffusion device. The controller 188 iscoupled to one or more temperature sensors (not shown but installedproximate and/or on the heating element(s) 196) to measure thetemperature of the element(s) 196 and send feedback to the controller188, which determines whether to increase or decrease the temperaturebased on the desired intensity setting, which may be stored in statesettings in a non-transitory memory device coupled to the controller188. The intensity setting may be variable based on the time of day orother parameters, and/or user-defined using the scent application 108,as discussed elsewhere herein.

In some embodiments, the diffusion device uses the above described PWMoutput control and temperature input data in conjunction with a PID(proportional, integral, derivative) control loop firmware algorithm.This is beneficial as it can increase the reliability, robustness, andruggedness of the diffusion device. With proper system tuning, the PIDcontrol can help to ensure that the temperature will more accuratelytrack the desired set point, with less over/undershoot. For instance,the following example code could be used by the controller 188.

Previous_error = θ integral = θ start:  error = setpoint -measured_value  integral = integral + error*dt  derivative = (error -previous_error)/dt  output = Kp*error + Ki*integral + Kd*derivative previous_error = error  wait(dt)  goto start

In further embodiments, in additional and/or alternative to a PID loop,the firmware may program the controller 188 to use a PI loop or othersuitable feedback control loops to control the temperature.

As discussed herein regarding the inventive intensity control performedby the controller 188 in conjunction with the heating element(s) 196,the scent dispensation may be digitally controlled through pulse widthmodulation (PWM). In some embodiments, the heating element switchingdiscussed herein may also utilize the same or similar hardware and/orsoftware to carry out those operations.

In some embodiments, through algorithmic direction from the instance ofthe scent application 108 (e.g., smart phone app), via the cloudplatform described herein, and thereafter the dispenser’s firmware, thehardware may be instructed to set at least one vial diffuser (heatingelement) to a PWM of zero (thus turning it off) and at least one otherto some PWM value above zero (thus turning it on). Similar logic mayalso perform switching between vials 250. In this example, the scentapplication 108 software logic, dispenser management application 160software logic, and/or firmware 194 software logic may prevent and/orallow two or more vial diffusers (e.g., heating element circuitries)from being turned on simultaneously, although for other embodiments,they could be otherwise adapted if necessary.

In some embodiments, the firmware may program the controller to heatmultiple elements 196. In some embodiments, the heating of multipleelements 196 may be utilized to mix different scent solutions containedin different vials 250 installed int eh scent diffuser 132. In someembodiments, the heating of multiple elements 196 may be utilized tofurther increase the scent intensity in a given room in which the scentdispenser 132 is installed. Each scent solution may have a temperaturerange in which it can be effectively diffused (e.g., without causeburning of the scent solution). As such, a given heating element 196 mayhave a maximum rate at which a particular scent solution can diffused(maximum temperature the scent solution can be diffused).Advantageously, to increase diffusion beyond the maximum rate for agiven vial 250 and heating element 196, the controller 188 may actuate aplurality of heating elements (e.g., a first, a second, etc.) configuredto dispense the same scent solution. Further, a scent solution may havea particular temperature at which it optimally diffuses (e.g., below amaximal rate). Using plural heating elements allows the scent to diffuseat this rate while meeting the volume and/or intensity requirements of agiven room. The firmware may retrieve state settings (e.g., receivedfrom the dispenser management application 160) instructing thecontroller 198 to heat a plurality of wicks 252 at particulartemperatures, and the controller 188 may control the heating of theheating elements 196 accordingly. In further embodiments, the settingsfor different scents may be preloaded on the dispenser and the dispensermay adjust the heating of different scent solutions based on the storesettings. The state settings received from the dispenser managementapplication 160 may include data specifying which vial(s) to diffuse,the temperature at which to diffuse the solution from the vial, how longto diffuse the solution for, etc.

The controller 188 may listen for updated scent settings (e.g., bysending iterative requests to the dispenser management application 160,running a local server configured to listen for update requestsincluding state settings from the dispenser management application 160,etc.). Further, the controller may 188 send check-in requests to thedispenser management application 160 reporting the operational status ofthe dispenser 132.

In some embodiments, state settings for scent dispenser 132 operationare synchronized with the dispenser management application 160. Theinterface 190 may utilize any communication protocol that is suitable,such as 801.11 protocols (e.g., Bluetooth, Wi-FiTM, etc.).

The controller 188 may be programmed by the firmware to update the statesettings when a user modifies the settings using an instance of thescent application 108 operating on his/her user device. The scentapplication 108 may transmit new and/or updated settings to thedispenser management application 160, which is programmed to thensynchronize the settings with the scent dispenser 132 if applicable. Inaddition, if the scent dispenser 132 is ever turned off, and/or thestate settings are lost somehow (e.g., due to malfunction or powerdisruption), the scent dispenser may be reinitialized (e.g., by thecontroller 188 downloading the state settings and configuring thehardware of the scent dispenser 132 based on the settings). Thecontroller 188 may receive settings via the interface 190 and update thesettings stored in the non-transitory memory of the scent dispenser 132.The non-transitory memory may be embedded in the controller 188 or maybe a separate device that is coupled to the controller 188. In someembodiments, the microcontroller may include MOSFET circuitry, theinterface 190, firmware, etc.

Any state information of the scent dispenser (e.g., the volume,available vials, vial in use, diffusion level, current LED color, etc.)can be communicated, via a wireless transceiver (e.g., the interface190) electronically coupled to the controller 188 that controls theabove-noted electrical components, via the network 102 (e.g., theInternet) to the server 150, which may relay the information via thenetwork 102 to the scent application 108 operating on a computing device106 of a user 112 (e.g., mobile device) that is associated with thatscent dispenser 132. This advantageously allows the user to view andreact to the information in real time.

In some embodiments, the controller 188 may be electronically coupled(e.g., wired, wirelessly) to a motion sensor 186 (e.g., a passiveinfrared sensor (PIR), photocell, other suitable motion sensor, etc.)reflecting the presence or absence of people within a room in whichscent dispenser(s) 132 are installed. The motion sensor 186 in somecases may be a device embedded in the scent dispenser 132 and/or may bea separate device that is installed in the premises and electronicallycoupled to the scent dispenser 132. Other variations are also possibleand contemplated.

Based on a predetermined duration of inactivity (e.g., no motiondetection signals received from the motion sensor 186), the controller132 may deactivate the heating elements 196 and suspend operation of thescent dispenser 132, or may reduce the diffusion intensity by a certainpercentage or to a certain minimal threshold, to economize the scentsolution. In the latter example, upon detecting motion within the roomvia the motion sensor 186 (e.g., based on a detection signal receivedfrom the motion sensor 186), the controller 188 may restore and/orincrease diffusion. Data regarding presence in a given room through theday may be transmitted to the dispenser management application 160,stored as premises data 180 in the data store, and used to generateanalytics about user preferences, such as whether users prefer to scenta room even though users aren’t present, whether users prefer to scent aroom only if users are present, whether users prefer to maintain aminimal scent in a room if users aren’t present, etc. This may bedetermined using the usage data because the usage data may be timeand/or date coded so that the rate of use, as well as the time of day,day of week, etc., usage occurred may be determined by the dispensermanagement application 160.

In some embodiments, the controller 188 may receive wireless signalsbroadcasted by other devices within transmission range, determine if thesignals are broadcasted by other scent diffusers 132, process thestrength of the signals belonging to the other scent diffusers 132, andadjust scent diffusion based on the signal strength of other scentdiffusers 132 that satisfy a predetermined signal strength threshold, asdiscussed in further detail with reference to at least FIG. 8 .

FIGS. 3A and 3B depict various aspects of an example vial sensor 300.

In some embodiments, the vial (e.g., volume) sensor 300 may be a sensingdevice for determining the volume level of the vial. The vial volumesensor may include a sensor, which produces an electric field. As theliquid volume in the vial 250 changes, the sensor 300 detects a changein the electric field and correlates the change into a volume change.Predetermined coefficients may be used by the controller 188 and/or 328to perform the correlation and determine the vial volume reliably. Insome cases, the sensor 300 is a capacitive sensing device, which isadvantageous because it is inexpensive, robust, and uses a noncontactapproach which reduces the probability of failure of the component overtime due to the buildup of dirt, chemicals, etc. However, it should beunderstood that other ways of sensing the vial volume are alsoapplicable, such as resistive, transmission line techniques (e.g., aprobe sensor, etc.), and are encompassed by this disclosure.

FIG. 3A is a schematic diagram of an example vial sensor 300 and FIG. 3Bis a block diagram of the example vial sensor 300. As shown, the vialsensor 300 includes a plurality of pads 302 that are wired to acontroller 328. The pads 302 may belong to one or more arrays. As shown,the vial sensor 300 includes two arrays of pads 302 (those wired toports P2-0 through P2-5 and those wired to P0-2 through P0-7). Thecontroller 328 electrically charges the sensor pads 302 of each array,and detects a change in the signals received from the array, anddetermines a corresponding change in the fluid level of the scentedsolution of the vial.

A non-limiting example of the controller 328 may include an ARM-basedmicrocontroller, such as one manufactured by Cypress Semiconductor underPN CY8C4124LQl-443, although it should be understood that other chiparchitectures are also applicable, that the controller 328 may becombined with other processors, and/or that numerous other variationsare possible, contemplated, and applicable.

Further, as shown in FIG. 3B, the vial sensor 300 may include thecontroller 328 including pins 322 and a chip 330, resistors 324connecting various pins 322 of the controller 328 to first, second,etc., arrays 354 of pads 302 a-302 n (e.g., via wires 326), a set ofcapacitors 332 to regulate the voltage powering the controller 328, anda testing and/or firmware flashing module 334.

It should be understood that the shape and dimensions of the pads 302may vary based on implementation. Thus, while a certain number of pads(e.g., 6) of an array 322 are used by example to describe the vialsensor 300, any suitable number of pads 302 may be used to provide thefunctionality and benefits described herein. For Instance, the sensorpads 302 may be nested, narrower, larger, horizontally or verticallydisposed, place in a multidimensional array, etc.

In some embodiments, the wires 326, pads 302, and/or trace patterns 326may comprise a conductive material, such as metal (e.g., PCB copper).The controller 328 may be programmed using firmware, which may be storedin an embedded or separate non-transitory memory device and loaded uponinitialization of the scent dispenser 132. The firmware may program thecontroller 328 to sense the vials 250 as described herein, and providesensory output to the controller 188 and/or other components.

In an example embodiment, the pads 302 of an array 322 may be spaced 1-2mm apart and may include a plurality (e.g., 2, 3, 4, 5, 6, 7, 8, etc.)copper sensor pads, although other spacing dimensions, pad sizes, andnumber of pads may be used, as described elsewhere herein. In someinstances, various pads 302 (e.g., top and bottom corner pads) may beconnected through jumper options that allow for driven shield, ground,and normal sensor pad connection options. Further, sensor padconnections may be in series with in-line resistors to the chip pins 322of the controller 328.

The circuitry/electronics of the vial sensor 300 may include resistors324 between the pins of the microprocessor 328 and the sensor pads 302to adjust the current being applied to the sensor pads 302 so theyconsistently charge to a level that allows for an electric field emittedby them to pass through the air between the sensor pads 302 and anadjacent vial sidewall 266 so the presence and/or absence of a solutioncontained in the vial 250 adjacent to the pad 302 may be detected.Further electronics of the vial sensor 300 may include resistors 324located near the line of where a center line of an H-shaped vial sensor300 meets a sensor region; l2C PSOC connections for tuner connectivity;digital ground pours on top/bottom of the PSOC mounting area, etc.,although other variations are also possible and contemplated.

FIGS. 4A-4D are block diagrams depicting a progression for sensing asolution level of vial(s) 250 using a vial sensor 300. In FIG. 4A, thevial 250 is relatively full (e.g., 80%) of scent solution 250. The arrayof sensor pads 302 are electrically coupled to a controller and charged.A sidewall of each vial 250 is situated adjacent to a correspondingarray 320 of sensor pads 302 (e.g., at a certain distance, which maypredefined) within an array of electric fields 322. The array 320 ofsensor pads 302 are electrically charged by the microcontroller 128(responsive to an actuation signal from the controller 188 using powerfrom the PS 184) to produce the array 322 of electric fields. Thecontroller 328 detects changes in one or more of the electric fields 322of the array as the solution 310 is dispensed from the correspondingvial 250 (responsive to heating by a corresponding heating element 196).

The vial sensor 300 may include any number of (e.g., two or more) arrays322 of sensor pads 302 that are respectively arranged in alignment withthe (e.g., two or more) vials 250 retained by the (e.g., two or more)vial couplings (e.g., coupling device(s) 244). For instance, arrays 320of sensor pads 302 may be situated along various sides (e.g., first,second, left, right, middle, etc.) of the vial sensor 300. Each array320 of sensor pads 302 may be arranged in alignment with a correspondingvial 250 retained by a corresponding vial coupling, such as a vialcoupling of the retaining mechanism 246. In embodiments, with multiplevials 250, the controller 328 charges multiple arrays 322 to sense thefill level of those vials 250.

As the solution is used up 310, and the fill level (also called fluidlevel or solution level) goes down, the signals provided by the sensorpads 302 change. For example, the signals 306 that are output to thecontroller 328 and/or 188 in FIG. 4A reflect that the bottom four sensorpads 302 detect a maximum capacitance reflecting that the portions ofthe vial 250 corresponding in location to those sensor pads 302 arefull. However, the top two sensor pads 302 detect a minimum capacitancereflecting that the portions of the vial 250 corresponding in locationto those sensor pads 302 are empty. The controller 328 and/or 188 mayaggregate the signals and determine an overall fill level (e.g., 80%,50%, 20%, 1%, etc.). As the solution is dispensed during operation, thesolution level 310 drops, and as a result, the output to the controller306 changes (e.g., in FIG. 4B, three pads register a minimumcapacitance, one registers an high capacitance (e.g., less than themaximum but closer to the maximum than the minimum), and three registera maximum capacitance; in FIG. 4C, five pads register a minimumcapacitance and two pads register a maximum capacitance; and in FIG. 4D,six pads register a minimum capacitance and one pad registers a lowcapacitance due to a trace amount of solution being left in the vial250). The controller 188 may transmit usage data, such as the rate atwhich the solution of each vial drops, as determined using data from thevial sensor 300, to the dispenser management application 160 for storageand/or use in generating analtyics, as described in further detailherein. In some embodiments, the output 306 may be output on a cycle,such as the duty cycle of the controller 328 and/or 188, although othertiming variations are also possible and contemplated.

The controller 328 may detect changes in the one or more of the electricfields 322 as the solution 310 is dispensed from the corresponding vial250. For clarity, the term controller, as used herein, may refer to thecontroller 188, the controller 328, or both the controller 188 and thecontroller 328, unless specifically described otherwise.

In some embodiments, the controller 188 may be electrically coupled toheating element(s) 196 and electrically coupled to array(s) of sensorpads 302 via the controller 328. The controller 188 may regulate thetemperature level of the heating element(s) 196, and the controller 328may receive signals from the array(s) 322 of sensor pads 302, andprovide the signals to the controller 188 for processing. The controller188 may process the signals to determine a fluid level of the vial(s)250 and/or may relay the signals to dispenser management application160, which may store the signals as usage data 178 in association withthe scent dispenser 132 and/or vial(s) 250 and/or scent being dispensed(using their corresponding IDs). In some cases, a change in a signalreceived from a pad 302 may reflect a change in capacitance due to areduction in the solution near the pad 302.

The controller 188 may be programmed to switch between, and or includemultiple, vials 250 in implementation where a plurality of heatingelements 196 and vial slots 222 are included in a scent dispenser 132.The circuitry of the heating elements 196 may include a switch mechanismallowing for independent control and/or heating of the heating elements196.

The heating element switching mechanism includes executable firmwarelogic and the switching circuitry of the heating elements 196. Theheating element switching mechanism is configured to switch between thedifferent solutions contained in the vials 250 so the scent dispenser132 can diffuse different scents at different times. The controller 188can control the operation of the heating element 196 based on auser-defined schedule or on-demand based on a user instruction submittedvia the scent application 108 operating on the user’s computer device106. In addition, in some cases, the controller 108 can automaticallyinstruct the heating element switching mechanism to switch from usingone vial 250 to another vial 250 when the first vial 250 has run out ofsolution. Once switched, the previously active heating element 196 isswitched off and another heating element 196 is turned on, which resultsin the scent heated by the other heating element 196 to begin diffusionand the former to cease diffusion. Further, the switching mechanism canallow for multiple heating elements 196 to be active at the same time atthe same or different temperature levels, depending on the settingsreceived from the dispenser management application 160.

Additionally, the scent dispenser 132 described herein may furtheramplify the efficiency of switching between or to include multiplescents. In some embodiments, to do so, the scent dispenser 132 utilizesa combination of additional software logic and the inclusion of barand/or detectable objects (e.g., QR codes) on the vials 250. FIG. 13depicts an example vial 1300 that includes an example detectable object1302. The scent dispenser 132 may include an optical sensor to capturethe detectable object 1302 and determine the identity of the vial 1300based thereon.

In an example, a camera, scanner, etc., included on the main board 235may scan a vial 250 upon insertion into a slot of the scent dispenser132. The controller 188 may receive the captured data and identify thevial 250, and/or send the captured data to the dispenser managementapplication 160, which may in turn identify the vial 250 and indicatethe slot in which the vial 250 is installed. Upon identification of thevial 250, the controller 188 may load the scent diffusion settings forthat vial 250 and slot (e.g., heating element 196), such as thetemperature, heating duration, whether to actuate other output devices192 and the parameters for actuating those output devices 192 (e.g.,LEDs, audio reproduction device(s), etc.).

In another example, upon the user receiving a new vial refill, the scentapplication 108 executing on the user’s mobile device may prompt theuser 112 to either manually select within the scent application 108 thecorrect scent of the their new refill, or alternatively, utilizing animage capture device of the user’s mobile device (e.g., the user’sphone’s bar code scanner/camera) to scan the detectable object, such asunique graphical image included on the vial 250 (e.g., the bar code, QRcode, etc., on the vial). The scent application 108 and/or the dispensermanagement application 160 may identify specifically which scentsolution the vial 250 contains and then associates it with the correctvial slot/insert position 222 in the dispenser 132 (e.g., by querying atable that includes this information using the unique identifierassociated with the unique graphical image). This scanning process addssimplicity for the user and also increases the integrity of thecollected data analytics. It also verifies which vials 250 are beingused and can prevent counterfeit vials 250 from being used. This isadvantageous, as some solutions that are homemade or non-authentic couldbe flammable, toxic, cause respiratory distress, or other issues.

In some embodiments, room profiles stored in the data store 170 and/orin a local memory, and may be used to control the level of diffusion andwhich scents are diffused by the scent dispenser over time. In addition,the room profile may include color and intensity settings for thedevices of the scent dispenser, such as one or more lights (e.g.., LEDs)included in the scent dispenser. The LED(s) may be variable LEDs thatcan produce virtually any color. These colors may be correlated with thescent being diffused from the different vials included in the scentdispenser to produce a different mood (relaxing, energetic, etc.) forthe room at different times of the day, times of year, etc. Thecontroller 188 may reference the state settings (e.g., reflecting theroom profile) to determine how to control the level of intensity ofdiffusion, which vial 250 should be active, the level of intensity ofthe output devices (e.g., LEDs), the characteristics of the outputdevices (e.g., color, sound, etc.). Additionally or alternatively, theuser may set the parameters of the output devices (e.g., intensity andcolor of the LED(s)), remotely using the scent application 108, whichthe scent dispenser may receive and then implement responsive toreceiving corresponding state settings from the dispenser managementapplicant 160.

FIG. 6 is a flowchart of an example method 600 for sensing vial volume.In block 602, the method charges the sensor array(s) 322, and in block604, the method 600 heats heating element(s) 196 that are fluidlyconnected to the vial(s) 250. In some embodiments, wick(s) 252 mayfluidly connect the heating element(s) 196 with the vial(s) 250. Infurther embodiments, the vial(s) 250 may be fluidly coupled to theheating element(s) 196 using other arrangements, such as heating thevial(s) 250 themselves, dripping scent solution into the vial(s) 250(e.g., using a gravity fed configuration where the vial(s) 250 are stillupside down), etc.

In block 606, if the method 600 receives signals from or more sensorarrays 322, the method 600 may proceed to determine the signal values inblock 608, compute vial fill level(s) using the signal values in block610, and transmit, in block 612, the vial fill level(s) to the dispensermanagement server 150 for processing and/or storage by the dispensermanagement application 160.

In block 614, the method 600 determines whether the dispenser 132 isstill active, and if so, proceeds to block 606 for another iteration.If, in block 614, the dispenser 132 is no longer active (e.g. thescheduled scent diffusion presented, the scent dispenser 132 isinactivated (sometimes referred to as turned off), a loss of poweroccurred, etc.), the method 600 returns to block 616 and awaitsactuation of the scent dispenser 132. Method 600 may check (e.g.,routinely, etc.) to see whether an actuation signal has been received,and upon receiving an actuation signal (e.g., responsive to a timertriggering, responsive to receiving state settings from the dispensermanagement application 160, etc.), may return to block 602 and repeatthe method 600. If in block 608, the signals of the received from thesensor array(s) 322, the method 600 may wait until the signals receivedbefore proceeding to block 608, and if too much time passes, may reportan error and exit. If, in block 618, no actuation signal is beenreceived, the method 600 may continue to stay active and wait for anactuation signal to proceed.

FIG. 7A is flowchart of an example method 700 for activating a vial 250.In block 702, the scent application 108 may receive a vial identifierfor the vial 250. For example, using the user interface, the user 112may enter the vial identifier using an input device of a user device 106that is executing the scent application 108. In a further example, theuser may capture an image object include on the vial 250, and the scentapplication 108 may process the captured image object to determine thevial identifier. Other variations are also possible and contemplated.

In block 704, the scent application 108 may identify the scent dispenser132. For example, the user may input an identification of the scentdispenser 132 into which the user intends to install/has installed thevial 250, or the scent application 108, using fill level data for thescent dispensers 132 registered to the user 112. Based on the datastored in the data store 170, the scent application 108 may provide alist of empty vials 250 that are installed in the scent dispensers 132,and/or suggest the user replaceable of those vials 250 with the vial 250corresponding to the vial identifier specified in block 702.

Upon identifying the scent dispenser 132 into which the vial 250 is tobe installed, the scent application 108 determines, in block 706, intowhich slot 222 of the scent dispenser 132 user intends to install/hasinstalled the vial 250. This may be based on a user selection of theslot 222 using an input device of the user device 112 and acorresponding user interface presented by the scent application 108,and/or based on a recommendation to the user on which vial 250 toreplace based on the fill levels of the determined scent dispenser 132.

In block 708, the scent application 108 and/or the dispenser managementapplication 160 may associate the vial 250 with the determined slot 222of the scent dispenser 132. For example, the dispenser managementapplication 160 may store dispenser data reflecting the installation ofscent in the slot 222 and/or associating a unique vial identifier withthe slot 222. This information may be used to generate analytics, oftenin conjunction with a multiplicity of other users, to determine userscent preferences behavior and generate corresponding datavisualizations and graphical user interfaces for navigating theanalytics.

FIG. 7B is flowchart of a further example method 750 for activating avial 250. In block 752, a sensor 186 of the dispenser 132 detects thatthe vial 250 is inserted into one of the slots of the scent dispenser132. In some embodiments, the vial sensor 300 may detect the presence ofthe vial due to a large change in capacitance. In some embodiments, anoptical sensor may detect the change in light, and RF reader may detectthe presence of a corresponding RF tag included on the vial 250, or atouch sensor may detect the presence of the vial 250 by coming intocontact with it. Other variations are also possible and contemplated.

In block 754, the sensor 186 may capture the unique identifier of thevial 250. In some embodiments, the unique identifier may be embodied byan optical representation included on the vial 250, such as onescannable using an optical sensor. In some embodiments, the uniqueidentifier may be transmitted via radio frequency responsive to an RFtag being placed proximate to an RF reader. In some embodiments, thecolor of the vial 250, or some other visual representation, may becaptured by sensor 186 of the scent dispenser 132 and used as and/orprocessed into a unique identifier. As shown in FIG. 13 , and anembodiment may use a QR code 1302, and the sensor 26 may be a scannerconfigured to scan and interpret the QR code 1302.

In block 756, the sensor 186 and/or the controller 188 may process thecaptured data to identify the vial 250. Some embodiments, the controller188 may cooperate with the dispenser management application 160 todecrypt the captured data and determine a unique identifier for thevial. In block 758, the controller 188 and/or the dispenser managementapplication 160 may use the unique identifier for the vial 250 to verifythe viability of the vial. For example, if the vial 250 is brand-new,the data store 170 may include data reflecting the existence of the vial250 and that the vial 250 is never been used and are installed in ascent dispenser 132. In another example, the vial 250 has been partiallyused, the data store 170 will include usage data reflecting that usageand that the vial 250 has never been used to depletion, and as such,will allow for continued use of the vial 250 (e.g., provided in somecases that the scent solution included in the vial 250 is unexpired). Ina further example, if the usage data stored in the data store 170reflects that the vial 250 in use is used to completion, or in otherwords all of the scent solution have been used, then the dispensermanagement application 160 and/or the controller 188 may prevent thescent dispenser 132 from dispensing scent from the vial 250. Further,the dispenser management application 160 may detect when a vial 250might somehow go from the 50% fill level to an 80% fill level based onsensor data received from a vial sensor 322, thus indicating that a usermay have filled the vial 250 with additional solution. In this case,since heating the unknown solution could yield harmful effects, thedispenser management application 160 and/or the controller 180 mayprevent usage of the vial 250 in the scent dispenser 132.

In block 760, the scent application 108 and/or the dispenser managementapplication 160 may associate the vial 250 with the determined slot 222of the scent dispenser 132. For example, the dispenser managementapplication 160 may store dispenser data reflecting the installation ofscent in the slot 322 and/or associating a unique vial identifier withthe slot 222. This information may be used to generate analytics, oftenin conjunction with a multiplicity of other users, to determine userscent preferences behavior and generate corresponding datavisualizations and graphical user interfaces for navigating theanalytics.

FIG. 8 is a flowchart of an example method 800 for automaticallyadjusting the dispensation intensity of a scent dispenser 132 based onthe presence of nearby scent dispensers 132.

In block 802, the controller 188 of the first scent dispenser 132enables an interface 190 of the first scent dispenser 132, and upondoing so, receives in block 804, wireless local area network (WLAN)transmissions from other devices within transmission rate. In block 806,the controller 188 identifies one or more second scent dispensers 132based on the WLAN transmissions. In some embodiments, the transmissionmay include identifying data reflecting that the device is a scentdispenser 132 and/or the scent dispenser 132 is actively dispensing.Some embodiments, that identified data may be encrypted, and thecontroller 188 may decrypt the data for security reasons.

In block 808, the controller 188 of the first scent dispenser 132 mayprocess the signals by broadcasted by the identified second scentdispenser(s) 132 to determine the strength of the signals, and based onthe strength of the signals, may determine, in block 810, distance(s)between the second scent dispenser(s) 132 and the first scent dispenser132.

Based on the distance(s), the controller 188 may, in block 812, adjustan intensity level at which or more scent is being dispensed by thefirst scent dispenser 132. For example, the controller 188 may have apredefined set of rules correlating scent intensity and a density ofscent dispensers 132, and the controller 188 may utilize this data toadjust the intensity level. In a further example, the controller 188 mayutilize thresholds reflecting intensity level relative to distance fromother scent dispensers 132, and may use the thresholds to adapt scentintensity. In further embodiments, the first scent dispenser 132 maytransmit data reflecting the environment including the neighboringsecond scent dispenser(s) 132 and their dispensing activity, and thedispenser management application 160 may send state settings to one ormore of the second scent dispenser(s) 132 to adjust the scentdispensation levels of those dispenser(s) 132. In some instances,sending state settings may include calling functions surfaced by thescent dispenser 132 using various parameters, as discussed elsewhereherein.

FIG. 9 is a flowchart of an example method 900 for adjusting thedispensation intensity of a scent dispenser 132 based on room size. Inblock 902, the scent application 108 may receive input from the userindicating a room size of a room. For example, the user may input thedimensions of a room using a corresponding interface of the scentapplication 108 and an input device of the user’s computing device 106.In block 904, the scent application 108 may receive input associatingthe scent dispenser 132 with a particular room. For example, the user,using a corresponding interface of the scent application 108 and aninput device of the user’s computing device 106, may select a room typefrom a predefined list of from types and enter a custom name for theroom, although other variations are also possible.

In block 906, based on the room size determined in block 902, thedispenser management application 160 may determine a number of vials touse for dispensing scent solution in that room, and may transmitcorresponding state settings to the scent dispenser 132. The scentdispenser 132, upon receiving the state settings, may, in block 908,activate the heating elements 196 corresponding to the number of vialsdetermined in block 906. This is advantageous for a larger room whichrequire a scent dispenser 132 to diffuse scent from more than one vial250 so that the scent level in the room is adequate. This is alsoadvantageous for smaller rooms which may require less scent diffusion,and thus fewer heating elements to be activated.

FIG. 10 is a flowchart of an example method 1000 for controllingoperation of scent dispenser(s) based on geolocation data.

In block 1002, a scent application may receive input(s) defininggeofence settings for scent dispensers 132 installed on particularpremises for one or more users (e.g., as reflected by unique user IDs).For example, the user may input, using a graphical user interfacedisplaying a map, the area of the geofence, which may be represented asan overlay in the graphical user interface.

In block 1004, the scent application 108 may transmit the geofencesettings to the dispenser management application 160, which may storethe settings as user data in the data store 170 in association with theuser(s) (e.g., using the user IDs).

In block 1006, the dispenser management application 160 may receivegeolocation data from a location-aware device associated with aparticular user ID (e.g., the user’s smartphone), such as one associatedwith the geofence data stored in block 1004. In block 1008, thedispenser management application 160 compares the geo-location dataassociated with the particular user ID with the geofence settings storedfor that particular user ID in the data store 170, and based on thecomparison determines whether a geolocation of the user is within thegeofence. If the geolocation is not within the geofence, the method 1000may return to block 1006 to receive updated geo-location data. If thegeolocation is within the geofence, the dispenser management application160 may determine whether the geofence criteria of another user ID isassociated with a particular user ID in the data store for the samepremises already satisfied that geofence criteria and that a scentprofile of another user 112 in use (e.g., a first scent is beingdispensed by a particular scent dispenser 132 in a particular room thepremises according to the settings of that user).

If the determination in block 1010 is negative, the dispenser managementapplication 160 and generate and send state settings based on the scentprofile that particular user associated with particular user ID (e.g. asreflected by the user data associated with that particular user ID inthe data store 170), and send the state settings to one or more scentdispensers 132 of the premises associated with a particular user ID sothe scent dispensers 132 can be configured according to the settings ofthat particular user, as reflected by the scent profile that particularuser.

If the determination in block 1010 is affirmative, the dispensermanagement application 160 determines which user has priority in block1014, and if the other user (the scent profile is currently in use) haspriority, continues to use a scent profile of the other user 1016 (e.g.,does not affect the current operation of the scent dispenser(s) 132) ofthe premises. In some embodiments, the scent profiles of the particularuser and the other user may not conflict for particular premises (e.g.,users have selected devices in different rooms for use), in which caseboth scent profiles may be supported in the conflict resolution may berequired. In other words, state settings reflecting the scent profilethe particular user can be sent to certain scent dispensers 132 at thepremises without affecting the scent dispensation currently occurringwithin the premises for the other user (e.g., by other scent dispensers132).

In some embodiments, the dispenser management application 160 may usethe geofence settings stored in block 1004 for automatically turning thescent dispensers 132 of a given premises on or off (active or inactive)based on whether or not a particular user this present at the premisesare not. For example, as the user leaves the premises, and the mobiledevice 106 of the user 112 leaves the geofence, the dispenser managementapplication 162 may transmit signals to the scent dispensers 132 in thepremises that are on to become inactive. Conversely, as the user’smobile device reenters the geofence upon returning to the premises, thedispenser management application 162 may transmit signals to the scentdispensers 132 in the premises to reactivate/wake-up based on theschedule data stored for the scent dispensers 132 in the data store 170,although other variations are also possible.

In some embodiment, geo-location data associated with a given user, suchas GPS data from a user’s 112 portable electronic device 106, can beused to further enhance the fragrance disbursement intelligence of thedispenser. For example, through the use of a low-power GPS mode, thescent application 108 operating on the user’s device can register anevent with the operating system of that device (e.g., iOSTM orAndroidTM) to be notified when the user leaves the approximate radius oftheir house and/or neighborhood. Upon receiving that event trigger,remote communication to the device may be established via the dispensermanagement application 160 and the dispenser 132 may be instructed toshut down all fragrance dispensing. The reverse process may occur whenthe user returns home.

The method 1000 and corresponding embodiments are advantageous as theycan automatically prevent wasted scent usage when the user is away fromhome (or office), and can be particularly helpful for individuals whoare frequently away from the premises or to balance scent dispensationin a premises in which multiple users reside. The scent application 108may further include settings to over-ride operation of the recoverymechanism, and/or adjust the operation thereof, as discusses elsewhereherein.

FIG. 11 is a flowchart of an example method 1100 for scheduling scentdispensation for room(s) of a premises. In block limited 1102, the scentapplication 108 receives input, for a given user ID, defining a setschedule for a set installed in a scent dispenser 132 in a room of apremises.

In block 1104, the scent application 108 may transmit the schedule datato the dispenser management application 160, which in turn may store thescent schedule in the data store 170 of the server 150 in associationwith the scent dispenser 132 (and other entities, user, premises, etc.).

In block 1106, the dispenser management application 160 may utilize theschedule data to monitor operation of the scent dispenser(s) 132 of thatpremises, and in block 1108, may detect an event based on the scentschedule. The event may indicate a particular scent dispenser and anaction for that scent dispenser.

In block 1110, if the event indicates to start active dispensation of ascent, dispenser management application 160, in block 1112, generatesand wirelessly transmits state settings instructing the scent dispenser132 to dispense the scent, and the controller 188 receives andimplements the state settings.

If, in block 1110, the determination is negative, the method 1100proceeds to block 1114, in which the dispenser management application160 determines whether to cease dispensing of the scent based on theevent. If the determination is affirmative, the dispenser managementapplication 160, in block 1116, generates and wirelessly transmits statesettings instructing the scent dispenser 132 to disable dispensing thescent, and the controller 188 receives and implements the statesettings.

If, in block 1114, the determination is negative, the method 1100proceeds to block 1118, in which the dispenser management application160 determines whether to switch between vials/switch scents. If thedetermination is affirmative, the dispenser management application 160,in block 1120, generates and wirelessly transmits state settingsinstructing the scent dispenser 132 to switch scents, and the controller188 receives and implements the state settings (e.g., by deactivatingone heating element 196 and activating another heating element 196 forheating a different scent).

Upon completion of blocks 1112, 1116, 1118 (assuming a negativedetermination), and/or 1120, the method 1100 may return to block 1106and repeat from there, and/or may exit.

FIG. 12A is a flowchart of an example method 1200 for activating a scentdispenser 132 based on detected motion. In block 1202, a motion sensorof the scent dispenser 132 may detect motion in the environment (e.g.,room) within range/surrounding the scent dispenser 132. Responsive tothe detected motion, the controller 132 may activate the scent dispenser132 (e.g. resume dispensing, query for current schedule and dispenseaccording to schedule, await instructions, etc.).

FIG. 12B is a flowchart of an example method 1250 for using motiondetection to control operation of a scent dispenser. In block 1206, amotion sensor of the scent dispenser 132 may monitor area. Thecontroller 188 may be coupled to the motion sensor and receive motiondata reflecting the presence or absence of motion within the area beingmonitored. In block 1208, the controller 188 may determine a room to bevacant based on the motion monitoring, which may reflect that there’sbeen no activity in the room for particular period of time (e.g., for atime threshold, no motion has been detected by the motion sensor). Inblock 1210, the controller 188 may suspend dispensing a scent based ondetermining the room to be vacant.

The foregoing description, for purpose of explanation, has beendescribed with reference to various embodiments and examples. However,the illustrative discussions above are not intended to be exhaustive orto limit the invention to the precise forms disclosed. Manymodifications and variations are possible in view of the aboveteachings. The various embodiments and examples were chosen anddescribed in order to best explain the principles of the invention andits practical applications, to thereby enable others skilled in the artto utilize the innovative technology with various modifications as maybe suited to the particular use contemplated. For instance, it should beunderstood that the technology described herein can be practiced withoutthese specific details in some cases. Further, various systems, devices,and structures are shown in block diagram form in order to avoidobscuring the description. For instance, various implementations aredescribed as having particular hardware, software, and user interfaces.However, the present disclosure applies to any type of computing devicethat can receive data and commands, and to any peripheral devicesproviding services.

In some instances, various implementations may be presented herein interms of algorithms and symbolic representations of operations on databits within a computer memory. An algorithm is here, and generally,conceived to be a self-consistent set of operations leading to a desiredresult. The operations are those requiring physical manipulations ofphysical quantities. Usually, though not necessarily, these quantitiestake the form of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the following discussion,it is appreciated that throughout this disclosure, discussions utilizingterms such as “processing,” “computing,” “calculating,” “determining,”“displaying,” or the like, refer to the action and methods of a computersystem that manipulates and transforms data represented as physical(electronic) quantities within the computer system’s registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission or display devices.

A data processing system suitable for storing and/or executing programcode, such as the computing system and/or devices discussed herein, mayinclude at least one processor coupled directly or indirectly to memoryelements through a system bus. The memory elements can include localmemory employed during actual execution of the program code, bulkstorage, and cache memories that provide temporary storage of at leastsome program code in order to reduce the number of times code must beretrieved from bulk storage during execution. Input or I/O devices canbe coupled to the system either directly or through intervening I/Ocontrollers. The data processing system may include an apparatus may bespecially constructed for the required purposes, or it may comprise ageneral-purpose computer selectively activated or reconfigured by acomputer program stored in the computer.

The foregoing description has been presented for the purposes ofillustration and description. It is not intended to be exhaustive or tolimit the specification to the precise form disclosed. Manymodifications and variations are possible in light of the aboveteaching. It is intended that the scope of the disclosure be limited notby this detailed description, but rather by the claims of thisapplication. As will be understood by those familiar with the art, thespecification may be embodied in other specific forms without departingfrom the spirit or essential characteristics thereof. Likewise, theparticular naming and division of the modules, routines, features,attributes, methodologies and other aspects may not be mandatory orsignificant, and the mechanisms that implement the specification or itsfeatures may have different names, divisions, and/or formats.

Furthermore, the modules, routines, features, attributes, methodologiesand other aspects of the disclosure can be implemented as software,hardware, firmware, or any combination of the foregoing. The technologycan also take the form of a computer program product accessible from acomputer-usable or computer-readable medium providing program code foruse by or in connection with a computer or any instruction executionsystem. Wherever a component, an example of which is a module or engine,of the specification is implemented as software, the component can beimplemented as a standalone program, as part of a larger program, as aplurality of separate programs, as a statically or dynamically linkedlibrary, as a kernel loadable module, as firmware, as resident software,as microcode, as a device driver, and/or in every and any other wayknown now or in the future. Additionally, the disclosure is in no waylimited to implementation in any specific programming language, or forany specific operating system or environment. Accordingly, thedisclosure is intended to be illustrative, but not limiting, of thescope of the subject matter set forth in the following claims.

What is claimed is:
 1. A fragrance management apparatus, comprising: adispensing container slot configured to retain a scent dispensingcontainer with a detectable identifying tag; a tag reader positionedwithin the dispensing container slot to detect the detectableidentifying tag when the scent dispensing container is positioned withinthe dispensing container slot; a non-volatile memory; and a controllerof a fragrance management apparatus, the controller configured toexecute instructions stored on the non-volatile memory to performoperations comprising: detecting, using the tag reader, a uniqueidentifier of the scent dispensing container based on the detectableidentifying tag of the scent dispensing container being placed proximateto the tag reader; and determining, using one or more processors, anidentity of the scent dispensing container based on the detected uniqueidentifier; and updating a scent profile to include the identity of thescent dispensing container.
 2. The fragrance management apparatus ofclaim 1, wherein the detectable identifying tag is a radio frequency(RF) tag and the tag reader is an RF reader.
 3. The fragrance managementapparatus of claim 1, wherein the detectable identifying tag is adetectable object and the tag reader is an optical sensor.
 4. Thefragrance management apparatus of claim 3, wherein the optical sensor isa camera and the detectable object is a QR code.
 5. The fragrancemanagement apparatus of claim 3, wherein the detectable identifying tagincludes a color and the optical sensor detects the color of thedetectable identifying tag.
 6. The fragrance management apparatus ofclaim 3, wherein the optical sensor is a light sensor and the lightsensor detects a presence of the scent dispensing container based on achange in a light reading captured by the light sensor.
 7. The fragrancemanagement apparatus of claim 1, wherein the tag reader is a touchsensor and the touch sensor detects a presence of the scent dispensingcontainer based on the touch sensor coming into contact with thedetectable identifying tag on the scent dispensing container.
 8. Thefragrance management apparatus of claim 1, wherein the controller isfurther configured to: verify a viability of the scent dispensingcontainer based on the identity.
 9. The fragrance management apparatusof claim 8, wherein verifying the viability of the scent dispensingcontainer includes one or more of verifying an age of the scentdispensing container, verifying a fill level of the scent dispensingcontainer, and verifying usage data of the scent dispensing container.10. The fragrance management apparatus of claim 9, wherein responsive toverifying the viability of the scent dispensing container, thecontroller is further configured to cause a scent dispensing element ofthe scent dispensing container to emit a scent.
 11. A fragrancemanagement apparatus, comprising: a dispensing container slot configuredto retain a scent dispensing container with an RF tag; an RF readerpositioned within the dispensing container slot proximate to the RF tagof the scent dispensing container when the scent dispensing container isretained in the dispensing container slot; a non-volatile memory; and acontroller of a fragrance management apparatus, the controllerconfigured to execute instructions stored on the non-volatile memory toperform operations comprising: detecting, using the RF reader, a uniqueidentifier of the scent dispensing container based on the RF tag of thecontainer being placed proximate to the RF reader; and determining,using one or more processors, an identity of the scent dispensingcontainer based on the detected unique identifier; and updating a scentprofile to include the identity of the scent dispensing container. 12.The fragrance management apparatus of claim 11, wherein the identity ofthe scent dispensing container is encrypted and determining the identityof the scent dispensing container further comprises decrypting theidentity of the scent dispensing container.
 13. The fragrance managementapparatus of claim 11, wherein the controller is further configured toverify usage data of the scent dispensing container based on theidentity of the scent dispensing container.
 14. The fragrance managementapparatus of claim 13, wherein the controller is further configured toverify that the scent dispensing container is new based on the verifiedusage data.
 15. The fragrance management apparatus of claim 13, whereinthe controller is further configured to verify that the scent dispensingcontainer is partially used based on the verified usage data.
 16. Thefragrance management apparatus of claim 13, wherein the controller isfurther configured to verify that the scent dispensing container hasbeen used to depletion based on the verified usage data.
 17. Thefragrance management apparatus of claim 13, wherein the controller isfurther configured to cause the scent dispenser to not emit a scentbased on the usage data being unverified.
 18. A method comprising:detecting, using an RF reader, a unique identifier of a scent dispensingcontainer based on an RF tag of the scent dispensing container beingplaced proximate to the RF reader; determining, using one or moreprocessors, an identity of the scent dispensing container based on thedetected unique identifier; updating, using the one or more processors,a scent profile to include the identity of the scent dispensingcontainer; and causing a scent dispenser to emit a scent from the scentdispensing container based on the updated scent profile.
 19. The methodof claim 18, further comprising: detecting an incompatible fill data ofthe scent dispensing container based on the updated scent profile; andcausing the scent dispenser to not emit the scent from the scentdispensing container based on the incompatible fill data.
 20. The methodof claim 18, wherein the scent profile includes one or more of a scentdispensing container configuration and settings for heating elementsbased on the scent profile.